Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-44948x86/mtrr: Check if fixed MTRRs exist before saving them

Description

In the Linux kernel, the following vulnerability has been resolved: x86/mtrr: Check if fixed MTRRs exist before saving them MTRRs have an obsolete fixed variant for fine grained caching control of the 640K-1MB region that uses separate MSRs. This fixed variant has a separate capability bit in the MTRR capability MSR. So far all x86 CPUs which support MTRR have this separate bit set, so it went unnoticed that mtrr_save_state() does not check the capability bit before accessing the fixed MTRR MSRs. Though on a CPU that does not support the fixed MTRR capability this results in a #GP. The #GP itself is harmless because the RDMSR fault is handled gracefully, but results in a WARN_ON(). Add the missing capability check to prevent this.

Timeline

  1. ID reserved

    By Linux

  2. · 14 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-44948, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 2b1f6278d77c1f2f669346fc2bb48012b5e9495a – < 34f36e6ee5bd7eff8b2adcd9fcaef369f752d82e
    • affected 2b1f6278d77c1f2f669346fc2bb48012b5e9495a – < 06c1de44d378ec5439db17bf476507d68589bfe9
    • affected 2b1f6278d77c1f2f669346fc2bb48012b5e9495a – < 450b6b22acdaac67a18eaf5ed498421ffcf10051
    • affected 2b1f6278d77c1f2f669346fc2bb48012b5e9495a – < ca7d00c5656d1791e28369919e3e10febe9c3b16
    • affected 2b1f6278d77c1f2f669346fc2bb48012b5e9495a – < 8aa79dfb216b865e96ff890bc4ea71650f9bc8d7
    • affected 2b1f6278d77c1f2f669346fc2bb48012b5e9495a – < 8a90d3fc7c24608548d3a750671f9dac21d1a462
    • affected 2b1f6278d77c1f2f669346fc2bb48012b5e9495a – < 388f1c954019f253a8383f7eb733f38d541e10b6
    • affected 2b1f6278d77c1f2f669346fc2bb48012b5e9495a – < 919f18f961c03d6694aa726c514184f2311a4614
  • Linux · Linux

    • affected 2.6.22
    • unaffected < 2.6.22
    • unaffected 4.19.320 – ≤ 4.19.*
    • unaffected 5.4.282 – ≤ 5.4.*
    • unaffected 5.10.224 – ≤ 5.10.*
    • unaffected 5.15.165 – ≤ 5.15.*
    • unaffected 6.1.105 – ≤ 6.1.*
    • unaffected 6.6.46 – ≤ 6.6.*
    • unaffected 6.10.5 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-44948 badge
[![CVE-2024-44948](https://cveledger.app/badge/CVE-2024-44948.svg)](https://cveledger.app/cve/CVE-2024-44948)

Record last updated .