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-2026-43171EFI/CPER: don't dump the entire memory region

Description

In the Linux kernel, the following vulnerability has been resolved: EFI/CPER: don't dump the entire memory region The current logic at cper_print_fw_err() doesn't check if the error record length is big enough to handle offset. On a bad firmware, if the ofset is above the actual record, length -= offset will underflow, making it dump the entire memory. The end result can be: - the logic taking a lot of time dumping large regions of memory; - data disclosure due to the memory dumps; - an OOPS, if it tries to dump an unmapped memory region. Fix it by checking if the section length is too small before doing a hex dump. [ rjw: Subject tweaks ]

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 6 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-2026-43171, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.12% · top 98% of all CVEs (18 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 3d8c11efd528d56972d44ed0de51c4e11a9a4fa9 – < 02de64ab54b4bb0f1b21bb324aeff3b08612be33
    • affected 3d8c11efd528d56972d44ed0de51c4e11a9a4fa9 – < 0e09b522f2622841389c3b2f9ac4969e35c0809d
    • affected 3d8c11efd528d56972d44ed0de51c4e11a9a4fa9 – < 64ae5aaa7ac93c83da456039e8ec747bfa8a7cff
    • affected 3d8c11efd528d56972d44ed0de51c4e11a9a4fa9 – < 5a9b1dda8481b82851a655c3bcc5b44879b95334
    • affected 3d8c11efd528d56972d44ed0de51c4e11a9a4fa9 – < 7780c0bad2a3a70a8c0113a33c02f4151d901eb3
    • affected 3d8c11efd528d56972d44ed0de51c4e11a9a4fa9 – < a8419f5f2c5f2d80848ddabb2b95cf0da84a5f91
    • affected 3d8c11efd528d56972d44ed0de51c4e11a9a4fa9 – < 54e131db4cdffd946db890ff33ff2647053fd4f6
    • affected 3d8c11efd528d56972d44ed0de51c4e11a9a4fa9 – < 55cc6fe5716f678f06bcb95140882dfa684464ec
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 5.10.252 – ≤ 5.10.*
    • unaffected 5.15.202 – ≤ 5.15.*
    • unaffected 6.1.165 – ≤ 6.1.*
    • unaffected 6.6.128 – ≤ 6.6.*
    • unaffected 6.12.75 – ≤ 6.12.*
    • unaffected 6.18.16 – ≤ 6.18.*
    • unaffected 6.19.6 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .