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-53214vfio/pci: Properly hide first-in-list PCIe extended capability

Description

In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Properly hide first-in-list PCIe extended capability There are cases where a PCIe extended capability should be hidden from the user. For example, an unknown capability (i.e., capability with ID greater than PCI_EXT_CAP_ID_MAX) or a capability that is intentionally chosen to be hidden from the user. Hiding a capability is done by virtualizing and modifying the 'Next Capability Offset' field of the previous capability so it points to the capability after the one that should be hidden. The special case where the first capability in the list should be hidden is handled differently because there is no previous capability that can be modified. In this case, the capability ID and version are zeroed while leaving the next pointer intact. This hides the capability and leaves an anchor for the rest of the capability list. However, today, hiding the first capability in the list is not done properly if the capability is unknown, as struct vfio_pci_core_device->pci_config_map is set to the capability ID during initialization but the capability ID is not properly checked later when used in vfio_config_do_rw(). This leads to the following warning [1] and to an out-of-bounds access to ecap_perms array. Fix it by checking cap_id in vfio_config_do_rw(), and if it is greater than PCI_EXT_CAP_ID_MAX, use an alternative struct perm_bits for direct read only access instead of the ecap_perms array. Note that this is safe since the above is the only case where cap_id can exceed PCI_EXT_CAP_ID_MAX (except for the special capabilities, which are already checked before). [1] WARNING: CPU: 118 PID: 5329 at drivers/vfio/pci/vfio_pci_config.c:1900 vfio_pci_config_rw+0x395/0x430 [vfio_pci_core] CPU: 118 UID: 0 PID: 5329 Comm: simx-qemu-syste Not tainted 6.12.0+ #1 (snip) Call Trace: <TASK> ? show_regs+0x69/0x80 ? __warn+0x8d/0x140 ? vfio_pci_config_rw+0x395/0x430 [vfio_pci_core] ? report_bug+0x18f/0x1a0 ? handle_bug+0x63/0xa0 ? exc_invalid_op+0x19/0x70 ? asm_exc_invalid_op+0x1b/0x20 ? vfio_pci_config_rw+0x395/0x430 [vfio_pci_core] ? vfio_pci_config_rw+0x244/0x430 [vfio_pci_core] vfio_pci_rw+0x101/0x1b0 [vfio_pci_core] vfio_pci_core_read+0x1d/0x30 [vfio_pci_core] vfio_device_fops_read+0x27/0x40 [vfio] vfs_read+0xbd/0x340 ? vfio_device_fops_unl_ioctl+0xbb/0x740 [vfio] ? __rseq_handle_notify_resume+0xa4/0x4b0 __x64_sys_pread64+0x96/0xc0 x64_sys_call+0x1c3d/0x20d0 do_syscall_64+0x4d/0x120 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Timeline

  1. ID reserved

    By Linux

  2. · 38 days later

    Published

  3. · 20 months 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-53214, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA-ADPADP (enrichment)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.26% · top 82% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – < 4464e5aa3aa4574063640f1082f7d7e323af8eb4
    • affected 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – < 7d121f66b67921fb3b95e0ea9856bfba53733e91
    • affected 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – < 0918f5643fc6c3f7801f4a22397d2cc09ba99207
    • affected 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – < 9567bd34aa3b986736c290c5bcba47e0182ac47a
    • affected 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – < 6c6502d944168cbd7e03a4a08ad6488f78d73485
    • affected 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – < 06f2fcf49854ad05a09d09e0dbee6544fff04695
    • affected 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – < 949bee8065a85a5c6607c624dc05b5bc17119699
    • affected 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – < 1ef195178fb552478eb2587df4ad3be14ef76507
    • affected 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – < fe4bf8d0b6716a423b16495d55b35d3fe515905d
  • Linux · Linux

    • affected 3.6
    • unaffected < 3.6
    • unaffected 4.19.325 – ≤ 4.19.*
    • unaffected 5.4.287 – ≤ 5.4.*
    • unaffected 5.10.231 – ≤ 5.10.*
    • unaffected 5.15.174 – ≤ 5.15.*
    • unaffected 6.1.120 – ≤ 6.1.*
    • unaffected 6.6.64 – ≤ 6.6.*
    • unaffected 6.11.11 – ≤ 6.11.*
    • unaffected 6.12.2 – ≤ 6.12.*
    • unaffected 6.13 – ≤ *

References

References11

Sources

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

Badge for a README or a ticket

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

Record last updated .