Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-50115: KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 2c4adc9b192a0815fe58a62bc0709449416cc884, 426682afec71ea3f889b972d038238807b9443e4, 58cb697d80e669c56197f703e188867c8c54c494; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 2c4adc9b192a0815fe58a62bc0709449416cc884, 426682afec71ea3f889b972d038238807b9443e4, 58cb697d80e669c56197f703e188867c8c54c494; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory Ignore nCR3[4:0] when loading PDPTEs from memory for nested SVM, as bits 4:0 of CR3 are ignored when PAE paging is used, and thus VMRUN doesn't enforce 32-byte alignment of nCR3. In the absolute worst case scenario, failure to ignore bits 4:0 can result in an out-of-bounds read, e.g. if the target page is at the end of a memslot, and the VMM isn't using guard pages. Per the APM: The CR3 register points to the base address of the page-directory-pointer table. The page-directory-pointer table is aligned on a 32-byte boundary, with the low 5 address bits 4:0 assumed to be 0. And the SDM's much more explicit: 4:0 Ignored Note, KVM gets this right when loading PDPTRs, it's only the nSVM flow that is broken.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Nov 5, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 15th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.1
CNA · Linux
8.4
1.3 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-50115

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.2 and later · before 5.10.229
  • linux linux kernel5.11 and later · before 5.15.170
  • linux linux kernel5.16 and later · before 6.1.115
  • linux linux kernel6.2 and later · before 6.6.59
  • linux linux kernel6.7 and later · before 6.11.6
  • linux linux kernel6.12

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.2affected
    • e4e517b4be019787ada4cbbce2f04570c21b0cbd and later · before 76ce386feb14ec9a460784fcd495d8432acce7a5affected · git
    • e4e517b4be019787ada4cbbce2f04570c21b0cbd and later · before 58cb697d80e669c56197f703e188867c8c54c494affected · git
    • e4e517b4be019787ada4cbbce2f04570c21b0cbd and later · before 6876793907cbe19d42e9edc8c3315a21e06c32aeaffected · git
    • e4e517b4be019787ada4cbbce2f04570c21b0cbd and later · before 2c4adc9b192a0815fe58a62bc0709449416cc884affected · git
    • e4e517b4be019787ada4cbbce2f04570c21b0cbd and later · before 426682afec71ea3f889b972d038238807b9443e4affected · git
    • e4e517b4be019787ada4cbbce2f04570c21b0cbd and later · before f559b2e9c5c5308850544ab59396b7d53cfc67bdaffected · git
    • before 3.2not affected · semver
    • 5.10.229 and later · up to and including 5.10.*not affected · semver
    • 5.15.170 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.4.0-503.19.1.el9_57.4.0-503.19.1.el9_5
AlmaLinux:9kernelbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64kbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-corebefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-debugbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-develbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-corebefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-cross-headersbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-debugbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-debug-corebefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-debug-develbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-50113Nov 5, 2024 · firewire: core: fix invalid port index for parent device
    22Monitor
  • ← EarlierCVE-2024-50114Nov 5, 2024 · KVM: arm64: Unregister redistributor for failed vCPU creation
    31Monitor
  • Later →CVE-2024-50116Nov 5, 2024 · nilfs2: fix kernel bug due to missing clearing of buffer delay flag
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2c4adc9b192a0815fe58a62bc0709449416cc884Vendor (CNA)
Linux Linux426682afec71ea3f889b972d038238807b9443e4Vendor (CNA)
Linux Linux58cb697d80e669c56197f703e188867c8c54c494Vendor (CNA)
Linux Linux6876793907cbe19d42e9edc8c3315a21e06c32aeVendor (CNA)
Linux Linux76ce386feb14ec9a460784fcd495d8432acce7a5Vendor (CNA)
Linux Linuxf559b2e9c5c5308850544ab59396b7d53cfc67bdVendor (CNA)
azl3 kernel 6.6.57.1-7 on Azure Linux 3.06.6.64.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.64.2-1 on Azure Linux 3.06.6.64.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.173.1-1 on CBL Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool7.4.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.115-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch646.4.0-150600.23.42.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-64kb6.4.0-150600.23.42.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-azure6.4.0-150600.8.31.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-debug6.4.0-150600.23.42.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default6.4.0-150600.23.42.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default-base6.4.0-150600.23.42.2.150600.12.18.4 · openSUSE:Leap 15.6Package registry (OSV)

+39

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records