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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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)
EPSS
2.1%
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 36× 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 143 total refreshes for this CVE.

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

Related CVEs(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 2.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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