CVE-2024-50022

Kernel panic via upward-rounded device-DAX fault offset

Published Oct 21, 2024 · Updated May 11, 2026

Incorrect address alignment in the Linux device-DAX fault path allows local users to cause a kernel panic through memory-error handling. In dax_set_mapping(), ALIGN() rounds an unaligned fault address upward instead of using ALIGN_DOWN(), so page_mapped_in_vma() checks the wrong page. Triggering requires an unpinned device-DAX region touched off its selected alignment and an injected machine-check memory error; repeated misidentification prevents termination of the responsible task and can panic the host.

CVSS severity5.5
Medium
EPSS probability0.27%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Incorrect address alignment in the Linux device-DAX fault path allows local users to cause a kernel panic through memory-error handling. In dax_set_mapping(), ALIGN() rounds an unaligned fault address upward instead of using ALIGN_DOWN(), so page_mapped_in_vma() checks the wrong page. Triggering requires an unpinned device-DAX region touched off its selected alignment and an injected machine-check memory error; repeated misidentification prevents termination of the responsible task and can panic the host.

The record

CVE
CVE-2024-50022
Published
Oct 21, 2024
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Oct 21, 2024CVE publishedPublication date reported by the CVE source.
  2. May 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.17
  2. Affected versionversion=b9b5777f09be84d0de472ded2253d2f5101427f2 <7fcbd9785d4c17ea533c42f20a9083a83f301fa6
  3. Affected versionversion=b9b5777f09be84d0de472ded2253d2f5101427f2 <9c4198dfdca818c5ce19c764d90eabd156bbc6da
  4. Affected versionversion=b9b5777f09be84d0de472ded2253d2f5101427f2 <b822007e8db341d6f175c645ed79866db501ad86
  5. Affected versionversion=b9b5777f09be84d0de472ded2253d2f5101427f2 <e877427d218159ac29c9326100920d24330c9ee6

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=5.17; version=b9b5777f09be84d0de472ded2253d2f5101427f2 <7fcbd9785d4c17ea533c42f20a9083a83f301fa6; version=b9b5777f09be84d0de472ded2253d2f5101427f2 <9c4198dfdca818c5ce19c764d90eabd156bbc6da; version=b9b5777f09be84d0de472ded2253d2f5101427f2 <b822007e8db341d6f175c645ed79866db501ad86; version=b9b5777f09be84d0de472ded2253d2f5101427f2 <e877427d218159ac29c9326100920d24330c9ee6

Published CVSS scores

5.5NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499.004Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo