CVE-2026-31715

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. 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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

f2fs: fix UAF caused by decrementing sbi->nr_pages[] in f2fs_write_end_io()

The xfstests case "generic/107" and syzbot have both reported a NULL pointer dereference.

The concurrent scenario that triggers the panic is as follows:

F2FS_WB_CP_DATA write callback umount

  • f2fs_write_checkpoint
  • f2fs_wait_on_all_pages(sbi, F2FS_WB_CP_DATA)
  • blk_mq_end_request
  • bio_endio
  • f2fs_write_end_io
: dec_page_count(sbi, F2FS_WB_CP_DATA) : wake_up(&sbi->cp_wait)
  • kill_f2fs_super
  • kill_block_super
  • f2fs_put_super
: iput(sbi->node_inode) : sbi->node_inode = NULL : f2fs_in_warm_node_list
  • is_node_folio // sbi->node_inode is NULL and panic

The root cause is that f2fs_put_super() calls iput(sbi->node_inode) and sets sbi->node_inode to NULL after sbi->nr_pages[F2FS_WB_CP_DATA] is decremented to zero. As a result, f2fs_in_warm_node_list() may dereference a NULL node_inode when checking whether a folio belongs to the node inode, leading to a panic.

This patch fixes the issue by calling f2fs_in_warm_node_list() before decrementing sbi->nr_pages[F2FS_WB_CP_DATA], thus preventing the use-after-free condition.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

May 1, 2026

Last Modified

June 19, 2026

Advisory Details (3)

Auto-updated May 6, 2026
No patch confirmed yet.
generic

f2fs: fix UAF caused by decrementing sbi->nr_pages[] in f2fs_write_end_io() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/963d2e24d9d92a31e6773b0f642214f10013ebf7
generic

f2fs: fix UAF caused by decrementing sbi->nr_pages[] in f2fs_write_end_io() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2d9c4a4ed4eef1f82c5b16b037aee8bad819fd53
generic

f2fs: fix UAF caused by decrementing sbi->nr_pages[] in f2fs_write_end_io() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/188bb65f247a7a7c62f287c9a263aee3cad96fa5

Vendor Advisories for CVE-2026-31715(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.259—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 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.86-1~bpo12+1 (19 versions)6.12.86-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.1-1~exp1 (129 versions)7.0.3-1—

Weakness Classification(1)

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

All Vendor Advisories

(18)

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 7× in last 7d / 72× 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 227 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-31715?
CVE-2026-31715 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: f2fs: fix UAF caused by decrementing sbi->nrpages[] in f2fswriteendio() The xfstests case "generic/107" and syzbot have both reported a NULL pointer dereference. The concurrent scenario that triggers the panic is as follows:…
When was CVE-2026-31715 disclosed?
CVE-2026-31715 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on June 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31715 actively exploited?
CVE-2026-31715 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 98.0% of all scored CVEs.
What is the CVSS score of CVE-2026-31715?
CVE-2026-31715 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31715?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31715, 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-2026-31715

Explore →

Is Your Infrastructure Affected by CVE-2026-31715?

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

Start Free Scan →Browse All CVEs