CVE-2026-31398

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-03. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-18778 (ENISA EUVD) · GHSA-pvqr-5pwq-xc53 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

mm/rmap: fix incorrect pte restoration for lazyfree folios

We batch unmap anonymous lazyfree folios by folio_unmap_pte_batch. If the batch has a mix of writable and non-writable bits, we may end up setting the entire batch writable. Fix this by respecting writable bit during batching.

Although on a successful unmap of a lazyfree folio, the soft-dirty bit is lost, preserve it on pte restoration by respecting the bit during batching, to make the fix consistent w.r.t both writable bit and soft-dirty bit.

I was able to write the below reproducer and crash the kernel. Explanation of reproducer (set 64K mTHP to always):

Fault in a 64K large folio. Split the VMA at mid-point with MADV_DONTFORK. fork() - parent points to the folio with 8 writable ptes and 8 non-writable ptes. Merge the VMAs with MADV_DOFORK so that folio_unmap_pte_batch() can determine all the 16 ptes as a batch. Do MADV_FREE on the range to mark the folio as lazyfree. Write to the memory to dirty the pte, eventually rmap will dirty the folio. Then trigger reclaim, we will hit the pte restoration path, and the kernel will crash with the trace given below.

The BUG happens at:

BUG_ON(atomic_inc_return(&ptc->anon_map_count) > 1 && rw);

The code path is asking for anonymous page to be mapped writable into the pagetable. The BUG_ON() firing implies that such a writable page has been mapped into the pagetables of more than one process, which breaks anonymous memory/CoW semantics.

[ 21.134473] kernel BUG at mm/page_table_check.c:118! [ 21.134497] Internal error: Oops - BUG: 00000000f2000800 [#1] SMP [ 21.135917] Modules linked in: [ 21.136085] CPU: 1 UID: 0 PID: 1735 Comm: dup-lazyfree Not tainted 7.0.0-rc1-00116-g018018a17770 #1028 PREEMPT [ 21.136858] Hardware name: linux,dummy-virt (DT) [ 21.137019] pstate: 21400005 (nzCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--) [ 21.137308] pc : page_table_check_set+0x28c/0x2a8 [ 21.137607] lr : page_table_check_set+0x134/0x2a8 [ 21.137885] sp : ffff80008a3b3340 [ 21.138124] x29: ffff80008a3b3340 x28: fffffdffc3d14400 x27: ffffd1a55e03d000 [ 21.138623] x26: 0040000000000040 x25: ffffd1a55f7dd000 x24: 0000000000000001 [ 21.139045] x23: 0000000000000001 x22: 0000000000000001 x21: ffffd1a55f217f30 [ 21.139629] x20: 0000000000134521 x19: 0000000000134519 x18: 005c43e000040000 [ 21.140027] x17: 0001400000000000 x16: 0001700000000000 x15: 000000000000ffff [ 21.140578] x14: 000000000000000c x13: 005c006000000000 x12: 0000000000000020 [ 21.140828] x11: 0000000000000000 x10: 005c000000000000 x9 : ffffd1a55c079ee0 [ 21.141077] x8 : 0000000000000001 x7 : 005c03e000040000 x6 : 000000004000ffff [ 21.141490] x5 : ffff00017fffce00 x4 : 0000000000000001 x3 : 0000000000000002 [ 21.141741] x2 : 0000000000134510 x1 : 0000000000000000 x0 : ffff0000c08228c0 [ 21.141991] Call trace: [ 21.142093] page_table_check_set+0x28c/0x2a8 (P) [ 21.142265] __page_table_check_ptes_set+0x144/0x1e8 [ 21.142441] __set_ptes_anysz.constprop.0+0x160/0x1a8 [ 21.142766] contpte_set_ptes+0xe8/0x140 [ 21.142907] try_to_unmap_one+0x10c4/0x10d0 [ 21.143177] rmap_walk_anon+0x100/0x250 [ 21.143315] try_to_unmap+0xa0/0xc8 [ 21.143441] shrink_folio_list+0x59c/0x18a8 [ 21.143759] shrink_lruvec+0x664/0xbf0 [ 21.144043] shrink_node+0x218/0x878 [ 21.144285] __node_reclaim.constprop.0+0x98/0x338 [ 21.144763] user_proactive_reclaim+0x2a4/0x340 [ 21.145056] reclaim_store+0x3c/0x60 [ 21.145216] dev_attr_store+0x20/0x40 [ 21.145585] sysfs_kf_write+0x84/0xa8 [ 21.145835] kernfs_fop_write_iter+0x130/0x1c8 [ 21.145994] vfs_write+0x2b8/0x368 [ 21.146119] ksys_write+0x70/0x110 [ 21.146240] __arm64_sys_write+0x24/0x38 [ 21.146380] invoke_syscall+0x50/0x120 [ 21.146513] el0_svc_common.constprop.0+0x48/0xf8 [ 21.146679] do_el0_svc+0x28/0x40 [ 21.146798] el0_svc+0x34/0x110 [ 21.146926] el0t ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

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

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA 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 SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

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

April 3, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated May 20, 2026
Patch available.
Web page

mm/rmap: fix incorrect pte restoration for lazyfree folios - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a0911ccdba41b0871abbf8412857bafedec3dbe1
Web page

mm/rmap: fix incorrect pte restoration for lazyfree folios - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/99888a4f340ca8e839a0524556bd4db76d63f4e0
Web page

mm/rmap: fix incorrect pte restoration for lazyfree folios - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/29f40594a28114b9a9bc87f6cf7bbee9609628f2

Vendor Advisories for CVE-2026-31398(1)

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 / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.18.20 (fixes >=6.15.0)—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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (123 versions)
  • every version up to 6.19.10-1: fixed in 6.19.10-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× 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.

Showing the most recent 95 of 241 refreshes on record for this CVE.

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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 146 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-30 07:49 UTCEG score recompute
  2. 2026-10-30 07:49 UTCGHSA enrichmentGHSA-pvqr-5pwq-xc53 · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  6. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-10-25 14:36 UTCEG score recompute
  8. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-23 23:59 UTCEG score recompute
  10. 2026-10-23 23:59 UTCGHSA enrichmentGHSA-pvqr-5pwq-xc53 · GitHub severity HIGH · GitHub CVSS 7.8
  11. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-10-18 03:48 UTCEG score recompute
  18. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-10-17 16:00 UTCEG score recompute
  20. 2026-10-17 16:00 UTCGHSA enrichmentGHSA-pvqr-5pwq-xc53 · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
Show 70 more
  1. 2026-10-12 16:15 UTCEG score recompute
  2. 2026-10-11 19:57 UTCEG score recompute
  3. 2026-10-11 17:11 UTCEG score recompute
  4. 2026-10-11 14:39 UTCEG score recompute
  5. 2026-10-11 02:31 UTCOSV refresh
  6. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  7. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-09-21 13:49 UTCOSV refresh
  19. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  26. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  27. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  28. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  29. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  30. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  31. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  32. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  33. 2026-09-02 11:14 UTCOSV refresh
  34. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  35. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  36. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  37. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  38. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  39. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  40. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  41. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  42. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  43. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  44. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  45. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  46. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  47. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  48. 2026-08-16 09:16 UTCEG score recompute
  49. 2026-08-16 09:16 UTCGHSA enrichmentGHSA-pvqr-5pwq-xc53 · GitHub severity HIGH · GitHub CVSS 7.8
  50. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  51. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  52. 2026-08-14 18:51 UTCGHSA enrichmentGHSA-pvqr-5pwq-xc53 · GitHub severity HIGH · GitHub CVSS 7.8
  53. 2026-08-14 05:42 UTCEG score recompute
  54. 2026-08-14 05:42 UTCGHSA enrichmentGHSA-pvqr-5pwq-xc53 · GitHub severity HIGH · GitHub CVSS 7.8
  55. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  56. 2026-08-13 09:55 UTCGHSA enrichmentGHSA-pvqr-5pwq-xc53 · GitHub severity HIGH · GitHub CVSS 7.8
  57. 2026-08-12 19:58 UTCEG score recompute
  58. 2026-08-12 19:58 UTCGHSA enrichmentGHSA-pvqr-5pwq-xc53 · GitHub severity HIGH · GitHub CVSS 7.8
  59. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  60. 2026-08-11 20:17 UTCEG score recompute
  61. 2026-08-11 20:17 UTCGHSA enrichmentGHSA-pvqr-5pwq-xc53 · GitHub severity HIGH · GitHub CVSS 7.8
  62. 2026-08-11 03:26 UTCEG score recompute
  63. 2026-08-11 03:26 UTCGHSA enrichmentGHSA-pvqr-5pwq-xc53 · GitHub severity HIGH · GitHub CVSS 7.8
  64. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  65. 2026-08-10 04:51 UTCGHSA enrichmentGHSA-pvqr-5pwq-xc53 · GitHub severity HIGH · GitHub CVSS 7.8
  66. 2026-08-09 17:02 UTCEG score recompute
  67. 2026-08-09 17:02 UTCGHSA enrichmentGHSA-pvqr-5pwq-xc53 · GitHub severity HIGH · GitHub CVSS 7.8
  68. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  69. 2026-08-09 05:13 UTCEG score recompute
  70. 2026-08-09 05:13 UTCGHSA enrichmentGHSA-pvqr-5pwq-xc53 · GitHub severity HIGH · GitHub CVSS 7.8

Frequently asked(5)

What is CVE-2026-31398?
CVE-2026-31398 is a high-severity vulnerability; its CVE record was published on April 3, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/rmap: fix incorrect pte restoration for lazyfree folios We batch unmap anonymous lazyfree folios by foliounmappte_batch. If the batch has a mix of writable and non-writable bits, we may end up setting the entire batch writable.…
When was the CVE record for CVE-2026-31398 published?
The CVE record for CVE-2026-31398 was published on April 3, 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 5, 2026; the record at its source may have been updated since.
Is CVE-2026-31398 actively exploited?
CVE-2026-31398 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-31398?
CVE-2026-31398 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31398?
A fix for CVE-2026-31398 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-31398 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-31398

Explore →

Is Your Infrastructure Affected by CVE-2026-31398?

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