CVE-2024-53214

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-12-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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: ? 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

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

December 27, 2024

Last Modified

August 5, 2026

Advisory Details (9)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

vfio/pci: Properly hide first-in-list PCIe extended capability - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fe4bf8d0b6716a423b16495d55b35d3fe515905d
generic

vfio/pci: Properly hide first-in-list PCIe extended capability - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1ef195178fb552478eb2587df4ad3be14ef76507
generic

vfio/pci: Properly hide first-in-list PCIe extended capability - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/949bee8065a85a5c6607c624dc05b5bc17119699
generic

vfio/pci: Properly hide first-in-list PCIe extended capability - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/06f2fcf49854ad05a09d09e0dbee6544fff04695
generic

vfio/pci: Properly hide first-in-list PCIe extended capability - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6c6502d944168cbd7e03a4a08ad6488f78d73485
generic

vfio/pci: Properly hide first-in-list PCIe extended capability - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9567bd34aa3b986736c290c5bcba47e0182ac47a
generic

vfio/pci: Properly hide first-in-list PCIe extended capability - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0918f5643fc6c3f7801f4a22397d2cc09ba99207
generic

vfio/pci: Properly hide first-in-list PCIe extended capability - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7d121f66b67921fb3b95e0ea9856bfba53733e91
generic

vfio/pci: Properly hide first-in-list PCIe extended capability - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4464e5aa3aa4574063640f1082f7d7e323af8eb4

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1044.48) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.135.133) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.211.231~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1033.33) @ jammy2026-05-23ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-05-23ubuntu
ubuntulinux-tools-gcp-fips (5.15.0.1079.69) @ jammy2026-05-23ubuntu
ubuntulinux-tools-kvm (5.15.0.1076.72) @ jammy2026-05-23ubuntu
ubuntulinux-tools-realtime (5.15.0.1080.83) @ jammy2026-05-23ubuntu
ubuntulinux-tools-aws-lts-20.04 (5.4.0.1142.139) @ focal2026-05-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1060 (5.4.0-1060.64) @ focal2026-05-23ubuntu
ubuntulinux-tools-fips (5.4.0.1116.113) @ focal2026-05-23ubuntu
ubuntulinux-tools-aws-edge (5.4.0.1142.152~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-tools-aws-fips (5.4.0.1142.89) @ focal2026-05-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.136.147~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-iot (5.4.0.1048.46) @ focal2026-05-23ubuntu
ubuntulinux-tools-azure-fde-edge (5.15.0.1086.95~20.04.1.61) @ focal2026-05-23ubuntu
ubuntulinux-virtual (6.8.0-58.60) @ noble2026-05-23ubuntu
ubuntulinux-tools-gcp-fips (5.4.0.1145.87) @ focal2026-05-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-05-23ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-05-23ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1010.12) @ noble2026-05-23ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1028.30~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1020.21) @ noble2026-05-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1074.77~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1077.83~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-ibm-edge (5.4.0.1090.95~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-58.60~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1081.90~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-05-23ubuntu
linuxKernel @ 4.19.325—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (44 versions)5.10.234-1—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1, 6.1.119-1~deb11u16.1.128-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (32 versions)6.1.123-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.12.3-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.12.3-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 165 total refreshes for this CVE.

  1. 2026-09-18 19:26 UTCEPSS rescore
  2. 2026-09-16 14:06 UTCEPSS rescore
  3. 2026-09-16 14:06 UTCEPSS rescore
  4. 2026-09-16 05:12 UTCEPSS rescore
  5. 2026-09-15 03:08 UTCEPSS rescore
  6. 2026-09-13 16:45 UTCEPSS rescore
  7. 2026-09-12 14:59 UTCEPSS rescore
  8. 2026-09-11 14:51 UTCEPSS rescore
  9. 2026-09-11 09:35 UTCEPSS rescore
  10. 2026-09-10 09:33 UTCEPSS rescore
  11. 2026-09-08 21:59 UTCEPSS rescore
  12. 2026-09-07 16:00 UTCEPSS rescore
  13. 2026-09-07 08:47 UTCOSV refresh
  14. 2026-09-06 13:46 UTCEPSS rescore
  15. 2026-09-04 13:59 UTCEPSS rescore
  16. 2026-09-04 05:05 UTCEPSS rescore
  17. 2026-09-02 14:10 UTCEPSS rescore
  18. 2026-09-01 13:52 UTCEPSS rescore
  19. 2026-08-30 19:16 UTCEPSS rescore
  20. 2026-08-30 19:16 UTCEPSS rescore
  21. 2026-08-30 01:21 UTCEPSS rescore
  22. 2026-08-28 21:39 UTCEPSS rescore
  23. 2026-08-27 14:24 UTCEPSS rescore
  24. 2026-08-26 14:44 UTCEPSS rescore
  25. 2026-08-25 13:47 UTCEPSS rescore
Show 75 more
  1. 2026-08-24 14:15 UTCEPSS rescore
  2. 2026-08-23 00:18 UTCEPSS rescore
  3. 2026-08-21 23:47 UTCEPSS rescore
  4. 2026-08-20 22:54 UTCEPSS rescore
  5. 2026-08-20 18:01 UTCOSV refresh
  6. 2026-08-19 17:02 UTCEPSS rescore
  7. 2026-08-18 13:47 UTCEPSS rescore
  8. 2026-08-17 13:45 UTCEPSS rescore
  9. 2026-08-16 14:55 UTCEPSS rescore
  10. 2026-08-16 02:13 UTCEPSS rescore
  11. 2026-08-15 01:29 UTCEPSS rescore
  12. 2026-08-13 21:59 UTCEPSS rescore
  13. 2026-08-12 13:49 UTCEPSS rescore
  14. 2026-08-11 13:41 UTCEPSS rescore
  15. 2026-08-10 23:58 UTCEPSS rescore
  16. 2026-08-09 13:45 UTCEPSS rescore
  17. 2026-08-08 16:35 UTCEPSS rescore
  18. 2026-08-07 16:26 UTCEPSS rescore
  19. 2026-08-06 13:45 UTCEPSS rescore
  20. 2026-08-05 19:16 UTCEPSS rescore
  21. 2026-08-05 11:50 UTCEG score recompute
  22. 2026-08-05 11:50 UTCVendor advisory
  23. 2026-08-05 11:50 UTCGHSA enrichment
  24. 2026-08-04 15:08 UTCEPSS rescore
  25. 2026-08-04 11:21 UTCEG score recompute
  26. 2026-08-04 11:21 UTCGHSA enrichment
  27. 2026-08-03 10:35 UTCEPSS rescore
  28. 2026-08-02 02:25 UTCEPSS rescore
  29. 2026-08-02 02:25 UTCEPSS rescore
  30. 2026-08-01 04:14 UTCEPSS rescore
  31. 2026-07-31 08:42 UTCOSV refresh
  32. 2026-07-30 16:26 UTCEPSS rescore
  33. 2026-07-30 16:26 UTCEPSS rescore
  34. 2026-07-30 01:29 UTCEPSS rescore
  35. 2026-07-28 15:35 UTCEPSS rescore
  36. 2026-07-26 14:53 UTCEPSS rescore
  37. 2026-07-25 14:17 UTCEPSS rescore
  38. 2026-07-25 14:17 UTCEPSS rescore
  39. 2026-07-23 14:17 UTCEPSS rescore
  40. 2026-07-23 14:17 UTCEPSS rescore
  41. 2026-07-23 02:43 UTCEG score recompute
  42. 2026-07-22 14:07 UTCEPSS rescore
  43. 2026-07-21 15:23 UTCEPSS rescore
  44. 2026-07-20 17:07 UTCEPSS rescore
  45. 2026-07-19 14:30 UTCEPSS rescore
  46. 2026-07-19 14:30 UTCEPSS rescore
  47. 2026-07-19 02:28 UTCEPSS rescore
  48. 2026-07-19 02:28 UTCEPSS rescore
  49. 2026-07-18 10:03 UTCEPSS rescore
  50. 2026-07-16 17:02 UTCEPSS rescore
  51. 2026-07-15 16:57 UTCEPSS rescore
  52. 2026-07-15 01:59 UTCEPSS rescore
  53. 2026-07-15 01:59 UTCEPSS rescore
  54. 2026-07-13 22:29 UTCEPSS rescore
  55. 2026-07-13 16:07 UTCOSV refresh
  56. 2026-07-13 06:12 UTCEPSS rescore
  57. 2026-07-12 05:45 UTCEPSS rescore
  58. 2026-07-11 08:26 UTCEPSS rescore
  59. 2026-07-09 19:09 UTCEPSS rescore
  60. 2026-07-09 19:09 UTCEPSS rescore
  61. 2026-07-08 15:14 UTCEPSS rescore
  62. 2026-07-07 13:45 UTCEPSS rescore
  63. 2026-07-07 13:45 UTCEPSS rescore
  64. 2026-07-06 16:26 UTCEPSS rescore
  65. 2026-07-06 16:26 UTCEPSS rescore
  66. 2026-07-06 02:22 UTCEPSS rescore
  67. 2026-07-05 02:29 UTCEPSS rescore
  68. 2026-07-04 06:30 UTCEPSS rescore
  69. 2026-07-04 06:30 UTCEPSS rescore
  70. 2026-07-01 15:06 UTCEPSS rescore
  71. 2026-06-30 23:21 UTCEPSS rescore
  72. 2026-06-30 23:21 UTCEPSS rescore
  73. 2026-06-29 14:05 UTCEPSS rescore
  74. 2026-06-28 14:07 UTCEPSS rescore
  75. 2026-06-28 04:55 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-53214?
CVE-2024-53214 is a high vulnerability published on December 27, 2024. 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…
When was CVE-2024-53214 disclosed?
CVE-2024-53214 was first published in the National Vulnerability Database on December 27, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-53214 actively exploited?
CVE-2024-53214 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.6% of all scored CVEs.
What is the CVSS score of CVE-2024-53214?
CVE-2024-53214 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-53214?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-53214, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-53214

Explore →

Is Your Infrastructure Affected by CVE-2024-53214?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs