CVE-2026-53191

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-39282 (ENISA EUVD) · GHSA-qhpr-79xw-32m8 (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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

io_uring/net: inherit IORING_CQE_F_BUF_MORE across bundle recv retries

When a bundle recv retries inside io_recv_finish(), the merge logic OR the saved cflags from the previous iteration with the cflags returned by the new iteration: cflags = req->cqe.flags | (cflags & CQE_F_MASK);

Bits listed in CQE_F_MASK are inherited from the new iteration, and all other bits (notably IORING_CQE_F_BUFFER and the buffer ID) come from the saved cflags. Before this change CQE_F_MASK covered only IORING_CQE_F_SOCK_NONEMPTY and IORING_CQE_F_MORE.

When using provided buffer rings (IOU_PBUF_RING_INC) with incremental mode, and bundle recv, io_kbuf_inc_commit() can leave the head ring entry partially consumed, __io_put_kbufs() then sets IORING_CQE_F_BUF_MORE on the returned cflags so userspace knows the buffer ID will be reused for subsequent completions.

Because IORING_CQE_F_BUF_MORE was not in CQE_F_MASK, the merge above silently dropped it whenever the final retry iteration partially consumed the buffer, and the subsequent req->cqe.flags = cflags & ~CQE_F_MASK save would have left a stale IORING_CQE_F_BUF_MORE in the carried-over cflags had one been present. Userspace would then wrongfully advance it ring head past an entry the kernel still uses.

Add IORING_CQE_F_BUF_MORE to CQE_F_MASK so it is both inherited from the new iteration into the user-visible CQE and stripped from the saved cflags between iterations.

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.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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.2%
EPSS %ILE
6th
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.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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 (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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 Vulnrichment) · Technical impact total (CISA Vulnrichment). 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

June 25, 2026

Last Modified

October 19, 2026

Advisory Details (4)

Auto-updated Jun 28, 2026
Patch available.
Web page

io_uring/net: inherit IORING_CQE_F_BUF_MORE across bundle recv retries - kernel/git/stable/linux.git - Linux kernel stable tree

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

io_uring/net: inherit IORING_CQE_F_BUF_MORE across bundle recv retries - kernel/git/stable/linux.git - Linux kernel stable tree

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

io_uring/net: inherit IORING_CQE_F_BUF_MORE across bundle recv retries - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4973232a67e4137ab9399f504f7f2bdd847f96d2
Web page

io_uring/net: inherit IORING_CQE_F_BUF_MORE across bundle recv retries - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0bbc9481f970b0b4ddb08cfa464db1cc93b74b56

Vendor Advisories for CVE-2026-53191(1)

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

Patch Availability(12)

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (146 versions)
  • every version up to 7.0.13-1: fixed in 7.0.13-1
—

Weakness Classification(1)

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

All Vendor Advisories

(11)

Data Freshness Timeline

(refreshed 11× in last 7d / 49× 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 100 of 277 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. None are among the latest 100 rows. The 177 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-53191?
CVE-2026-53191 is a high-severity vulnerability; its CVE record was published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: iouring/net: inherit IORINGCQEFBUF_MORE across bundle recv retries When a bundle recv retries inside iorecvfinish(), the merge logic OR the saved cflags from the previous iteration with the cflags returned by the new iteration:…
When was the CVE record for CVE-2026-53191 published?
The CVE record for CVE-2026-53191 was published on June 25, 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 October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-53191 actively exploited?
CVE-2026-53191 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53191?
CVE-2026-53191 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53191?
A fix for CVE-2026-53191 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53191 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-53191

Explore →

Is Your Infrastructure Affected by CVE-2026-53191?

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