CVE-2026-72458

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

apparmor: fix NULL pointer dereference in unpack_pdb

pdb->dfa could be NULL if unpack_dfa fails, causing a NULL pointer dereference.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 15, 2026

Last Modified

August 17, 2026

References (3)

Vendor Advisories for CVE-2026-72458(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-10-07ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1015.15) @ resolute2026-10-07ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-38.38) @ resolute2026-10-07ubuntu

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

All Vendor Advisories

(3)

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 8× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 85 are merged into the row they repeat.

  1. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-18 03:16 UTCEG score recompute
  4. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-10-12 15:41 UTCEG score recompute
  11. 2026-10-11 19:27 UTCEG score recompute
  12. 2026-10-11 16:43 UTCEG score recompute
  13. 2026-10-11 14:03 UTCEG score recompute
  14. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-10-07 06:51 UTCVendor advisory
  20. 2026-10-07 06:51 UTCGHSA enrichmentGHSA-2qpq-46v2-w4c7
  21. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-10-04 03:33 UTCGHSA enrichmentGHSA-2qpq-46v2-w4c7
  25. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 9th percentile
Show 56 more
  1. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-09-30 21:05 UTCEG score recompute
  3. 2026-09-30 21:05 UTCGHSA enrichmentGHSA-2qpq-46v2-w4c7
  4. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-09-27 08:32 UTCGHSA enrichmentGHSA-2qpq-46v2-w4c7
  8. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-09-23 22:13 UTCGHSA enrichmentGHSA-2qpq-46v2-w4c7
  10. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-09-20 19:01 UTCGHSA enrichmentGHSA-2qpq-46v2-w4c7
  14. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-09-17 15:47 UTCGHSA enrichmentGHSA-2qpq-46v2-w4c7
  16. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-09-14 12:13 UTCGHSA enrichmentGHSA-2qpq-46v2-w4c7
  20. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-09-11 08:59 UTCGHSA enrichmentGHSA-2qpq-46v2-w4c7
  23. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-09-08 05:46 UTCGHSA enrichmentGHSA-2qpq-46v2-w4c7
  26. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  27. 2026-09-05 02:11 UTCGHSA enrichmentGHSA-2qpq-46v2-w4c7
  28. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  29. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  30. 2026-09-01 22:58 UTCGHSA enrichmentGHSA-2qpq-46v2-w4c7
  31. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  32. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  33. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  34. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  35. 2026-08-29 19:45 UTCGHSA enrichmentGHSA-2qpq-46v2-w4c7
  36. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  37. 2026-08-26 16:26 UTCGHSA enrichmentGHSA-2qpq-46v2-w4c7
  38. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  39. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  40. 2026-08-23 12:54 UTCGHSA enrichmentGHSA-2qpq-46v2-w4c7
  41. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  42. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  43. 2026-08-20 09:41 UTCGHSA enrichmentGHSA-2qpq-46v2-w4c7
  44. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  45. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  46. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  47. 2026-08-17 06:28 UTCGHSA enrichmentGHSA-2qpq-46v2-w4c7
  48. 2026-08-17 06:22 UTCNVD update
  49. 2026-08-17 05:28 UTCEG score recompute
  50. 2026-08-17 05:28 UTCGHSA enrichmentGHSA-2qpq-46v2-w4c7
  51. 2026-08-17 05:25 UTCMITRE cvelistV5
  52. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  53. 2026-08-16 02:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  54. 2026-08-15 06:23 UTCNVD update
  55. 2026-08-15 06:03 UTCEG score recompute
  56. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2026-72458?
CVE-2026-72458 is a vulnerability whose severity is not yet rated; its CVE record was published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: apparmor: fix NULL pointer dereference in unpack_pdb pdb->dfa could be NULL if unpack_dfa fails, causing a NULL pointer dereference.
When was the CVE record for CVE-2026-72458 published?
The CVE record for CVE-2026-72458 was published on August 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 17, 2026; the record at its source may have been updated since.
Is CVE-2026-72458 actively exploited?
CVE-2026-72458 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-72458?
A fix for CVE-2026-72458 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-72458 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-72458

Explore →

Is Your Infrastructure Affected by CVE-2026-72458?

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

Book a Demo →Browse All CVEs