CVE-2026-98069

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-86722 (ENISA EUVD) · GHSA-8xjr-h523-r9wr (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
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.6%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net/rds: acquire the fastpath locks in rds_conn_shutdown()

rds_conn_shutdown() quiesces the transmit and receive-refill paths by waiting for RDS_IN_XMIT and RDS_RECV_REFILL to be sampled clear, and then runs the transport shutdown and rds_conn_path_reset(). Sampling the bits clear is not the same as owning them: the moment after the wait_event() returns, rds_send_xmit() can re-acquire RDS_IN_XMIT (or rds_ib_recv_refill() can re-acquire RDS_RECV_REFILL) and run concurrently with the teardown.

The sender does recheck the connection state after taking the lock, but that recheck is a classic store-buffering pattern: teardown writes the state and reads the bit while the sender writes the bit and reads the state. acquire_in_xmit() is only an acquire operation, so on weakly ordered architectures both sides can miss each other's write, and the transmit path then runs while the transport zeroes its rings (e.g. rds_ib_ring_init()) and rds_send_path_reset() rewrites the transmit state under it.

Oracle UEK fixed the same class of crashes - a 14-year tail of BUG_ON()s in rds_ib_sub_signaled(), unexpected op-codes and NULL dereferences in rds_ib_send_cqe_handler() during failover testing - by making the teardown path *acquire* the fastpath bit locks instead of testing them ("rds: Make sure transmit path and connection tear-down does not run concurrently"). Ownership of a single word is decided by RMW atomicity, so no cross-variable ordering is needed.

Do the same here: take both locks before calling the transport shutdown, hold them across rds_conn_path_reset(), and release them explicitly with a wake-up afterwards. Both are released with clear_bit_unlock(), so that the ring re-initialization done by the transport shutdown and the transmit state rewritten by rds_send_path_reset() are ordered before either bit is seen clear by the next acquire_in_xmit() or acquire_refill().

The fastpath users of these bits - rds_send_xmit() and rds_ib_recv_refill() - are trylock style and back off while teardown owns the locks, so no new lock dependency is introduced for them. rds_tcp_reset_callbacks() is different: since the previous patch it acquires RDS_IN_XMIT as well, and it blocks doing so, so its wait now spans the teardown instead of at most one send batch. That waiter runs from rds_tcp_accept_one() on the single-threaded krdsd workqueue and holds rds_tcp_accept_lock and t_conn_path_lock while it waits, so a duelling SYN accepted while its path is being torn down parks accept processing for the duration of the teardown - for TCP bounded by the (up to 5 s) drain loop in rds_tcp_conn_path_shutdown(). An IB path's drain in rds_ib_conn_path_shutdown() has no round cap, but no blocking waiter either: rds_tcp_reset_callbacks() is the only blocking acquirer of these bits and waits only on its own TCP path, and the fastpaths are trylock-and-back-off on both transports, so a long IB drain lengthens only that path's own quiesce. The window is narrow: the accept-side state check has to pass before the teardown moves the path to RDS_CONN_DISCONNECTING.

Because krdsd is a single global workqueue, everything else queued there - accept processing for other connections and network namespaces, and the flush_workqueue(rds_wq) in rds_tcp_listen_stop() during namespace teardown - waits behind the parked accept worker for that time. It cannot deadlock, although the waits do point at each other: the teardown blocks until the bit's holder releases it, and the holder may be that krdsd accept worker. The holder finishes without needing anything the teardown owns: the sync cancels rds_tcp_reset_callbacks() issues target cp_send_w and cp_recv_w on the path's ordered cp_wq, whose only execution slot is occupied by the blocked cp_down_w itself, so they are pending at most and cancel without flushing - a reliance on cp_wq being ordered that is now noted next to those cancels (on ---truncated---

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/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)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 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.6%
EPSS %ILE
47th
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 (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-18). 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, and whom BOD 26-04 binds: 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.

The score's inputs: 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

September 25, 2026

Last Modified

November 18, 2026

Advisory Details (4)

Auto-updated Sep 25, 2026
Patch available.
Web page

net/rds: acquire the fastpath locks in rds_conn_shutdown() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/813f3582ac7ae9f60f917937d54660e0952d5f2d
Web page

net/rds: acquire the fastpath locks in rds_conn_shutdown() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1fe627e5db5c3f53a9f9f9c8a66671755d306955
Web page

net/rds: acquire the fastpath locks in rds_conn_shutdown() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/900e96c9749a06833801f60c393aa1d405ea226c
Web page

net/rds: acquire the fastpath locks in rds_conn_shutdown() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7febb113795d5de5b690b208f4b0e64a5fad1201

Vendor Advisories for CVE-2026-98069(2)

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

Patch Availability(18)

These rows come from Ubuntu. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (57 versions)
  • every version up to 6.1.190-1: fixed in 6.1.190-1
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(18)

Data Freshness Timeline

(refreshed 9× in last 7d / 40× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 178 rows 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 78 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-98069?
CVE-2026-98069 is a high-severity vulnerability; its CVE record was published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net/rds: acquire the fastpath locks in rds_conn_shutdown() rds_conn_shutdown() quiesces the transmit and receive-refill paths by waiting for RDS_IN_XMIT and RDS_RECV_REFILL to be sampled clear, and then runs the transport shutdown…
When was the CVE record for CVE-2026-98069 published?
The CVE record for CVE-2026-98069 was published on September 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 November 18, 2026; the record at its source may have been updated since.
Is CVE-2026-98069 actively exploited?
CVE-2026-98069 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98069?
CVE-2026-98069 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-98069?
A fix for CVE-2026-98069 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98069 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-98069

Explore →

Is Your Infrastructure Affected by CVE-2026-98069?

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