CVE-2025-68260

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 2025-12-16. 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 — 3 sources updated this week

Also known asEUVD-2025-203744 (ENISA EUVD) · GHSA-jmw6-v428-xvcr (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 fixed version is listed under Patch Availability — apply it.

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

rust_binder: fix race condition on death_list

Rust Binder contains the following unsafe operation:

// SAFETY: A NodeDeath is never inserted into the death list // of any node other than its owner, so it is either in this // death list or in no death list. unsafe { node_inner.death_list.remove(self) };

This operation is unsafe because when touching the prev/next pointers of a list element, we have to ensure that no other thread is also touching them in parallel. If the node is present in the list that remove is called on, then that is fine because we have exclusive access to that list. If the node is not in any list, then it's also ok. But if it's present in a different list that may be accessed in parallel, then that may be a data race on the prev/next pointers.

And unfortunately that is exactly what is happening here. In Node::release, we:

  • Take the lock.
  • Move all items to a local list on the stack.
  • Drop the lock.
  • Iterate the local list on the stack.

Combined with threads using the unsafe remove method on the original list, this leads to memory corruption of the prev/next pointers. This leads to crashes like this one:

Unable to handle kernel paging request at virtual address 000bb9841bcac70e Mem abort info: ESR = 0x0000000096000044 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000044, ISS2 = 0x00000000 CM = 0, WnR = 1, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [000bb9841bcac70e] address between user and kernel address ranges Internal error: Oops: 0000000096000044 [#1] PREEMPT SMP google-cdd 538c004.gcdd: context saved(CPU:1) item - log_kevents is disabled Modules linked in: ... rust_binder CPU: 1 UID: 0 PID: 2092 Comm: kworker/1:178 Tainted: G S W OE 6.12.52-android16-5-g98debd5df505-4k #1 f94a6367396c5488d635708e43ee0c888d230b0b Tainted: [S]=CPU_OUT_OF_SPEC, [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE Hardware name: MUSTANG PVT 1.0 based on LGA (DT) Workqueue: events _RNvXs6_NtCsdfZWD8DztAw_6kernel9workqueueINtNtNtB7_4sync3arc3ArcNtNtCs8QPsHWIn21X_16rust_binder_main7process7ProcessEINtB5_15WorkItemPointerKy0_E3runB13_ [rust_binder] pstate: 23400005 (nzCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--) pc : _RNvXs3_NtCs8QPsHWIn21X_16rust_binder_main7processNtB5_7ProcessNtNtCsdfZWD8DztAw_6kernel9workqueue8WorkItem3run+0x450/0x11f8 [rust_binder] lr : _RNvXs3_NtCs8QPsHWIn21X_16rust_binder_main7processNtB5_7ProcessNtNtCsdfZWD8DztAw_6kernel9workqueue8WorkItem3run+0x464/0x11f8 [rust_binder] sp : ffffffc09b433ac0 x29: ffffffc09b433d30 x28: ffffff8821690000 x27: ffffffd40cbaa448 x26: ffffff8821690000 x25: 00000000ffffffff x24: ffffff88d0376578 x23: 0000000000000001 x22: ffffffc09b433c78 x21: ffffff88e8f9bf40 x20: ffffff88e8f9bf40 x19: ffffff882692b000 x18: ffffffd40f10bf00 x17: 00000000c006287d x16: 00000000c006287d x15: 00000000000003b0 x14: 0000000000000100 x13: 000000201cb79ae0 x12: fffffffffffffff0 x11: 0000000000000000 x10: 0000000000000001 x9 : 0000000000000000 x8 : b80bb9841bcac706 x7 : 0000000000000001 x6 : fffffffebee63f30 x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000 x2 : 0000000000004c31 x1 : ffffff88216900c0 x0 : ffffff88e8f9bf00 Call trace: _RNvXs3_NtCs8QPsHWIn21X_16rust_binder_main7processNtB5_7ProcessNtNtCsdfZWD8DztAw_6kernel9workqueue8WorkItem3run+0x450/0x11f8 [rust_binder bbc172b53665bbc815363b22e97e3f7e3fe971fc] process_scheduled_works+0x1c4/0x45c worker_thread+0x32c/0x3e8 kthread+0x11c/0x1c8 ret_from_fork+0x10/0x20 Code: 94218d85 b4000155 a94026a8 d10102a0 (f9000509) ---[ end trace 0000000000000000 ]---

Thus, modify Node::release to pop items directly off the original list.

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 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 fixed version is listed under Patch Availability. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
11th
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-11-05). 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 fixed version is listed under Patch Availability. 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

December 16, 2025

Last Modified

October 14, 2026

Advisory Details (2)

Auto-updated Jul 30, 2026
Fixed version listed under Patch Availability.
Web page

rust_binder: fix race condition on death_list - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3e0ae02ba831da2b707905f4e602e43f8507b8cc
Web page

rust_binder: fix race condition on death_list - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3428831264096d32f830a7fcfc7885dd263e511a

Vendor Advisories for CVE-2025-68260(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.1 (fixes >=6.18.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.

Data Freshness Timeline

(refreshed 9× in last 7d / 44× 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 99 of 242 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 143 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-68260?
CVE-2025-68260 is a high-severity vulnerability; its CVE record was published on December 16, 2025. In the Linux kernel, the following vulnerability has been resolved: rust_binder: fix race condition on death_list Rust Binder contains the following unsafe operation: // SAFETY: A NodeDeath is never inserted into the death list // of any node other than its owner, so it is either in this // death…
When was the CVE record for CVE-2025-68260 published?
The CVE record for CVE-2025-68260 was published on December 16, 2025. 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 14, 2026; the record at its source may have been updated since.
Is CVE-2025-68260 actively exploited?
CVE-2025-68260 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-68260?
CVE-2025-68260 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-2025-68260?
A fixed version for CVE-2025-68260 is listed under Patch Availability on this page: update to the version listed for your package. The vendor advisories EchelonGraph has for CVE-2025-68260 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-68260

Explore →

Is Your Infrastructure Affected by CVE-2025-68260?

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