CVE-2024-35969

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2024-05-20. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ipv6: fix race condition between ipv6_get_ifaddr and ipv6_del_addr

Although ipv6_get_ifaddr walks inet6_addr_lst under the RCU lock, it still means hlist_for_each_entry_rcu can return an item that got removed from the list. The memory itself of such item is not freed thanks to RCU but nothing guarantees the actual content of the memory is sane.

In particular, the reference count can be zero. This can happen if ipv6_del_addr is called in parallel. ipv6_del_addr removes the entry from inet6_addr_lst (hlist_del_init_rcu(&ifp->addr_lst)) and drops all references (__in6_ifa_put(ifp) + in6_ifa_put(ifp)). With bad enough timing, this can happen:

  • In ipv6_get_ifaddr, hlist_for_each_entry_rcu returns an entry.
  • Then, the whole ipv6_del_addr is executed for the given entry. The
reference count drops to zero and kfree_rcu is scheduled.
  • ipv6_get_ifaddr continues and tries to increments the reference count
(in6_ifa_hold).
  • The rcu is unlocked and the entry is freed.
  • The freed entry is returned.

Prevent increasing of the reference count in such case. The name in6_ifa_hold_safe is chosen to mimic the existing fib6_info_hold_safe.

[ 41.506330] refcount_t: addition on 0; use-after-free. [ 41.506760] WARNING: CPU: 0 PID: 595 at lib/refcount.c:25 refcount_warn_saturate+0xa5/0x130 [ 41.507413] Modules linked in: veth bridge stp llc [ 41.507821] CPU: 0 PID: 595 Comm: python3 Not tainted 6.9.0-rc2.main-00208-g49563be82afa #14 [ 41.508479] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) [ 41.509163] RIP: 0010:refcount_warn_saturate+0xa5/0x130 [ 41.509586] Code: ad ff 90 0f 0b 90 90 c3 cc cc cc cc 80 3d c0 30 ad 01 00 75 a0 c6 05 b7 30 ad 01 01 90 48 c7 c7 38 cc 7a 8c e8 cc 18 ad ff 90 <0f> 0b 90 90 c3 cc cc cc cc 80 3d 98 30 ad 01 00 0f 85 75 ff ff ff [ 41.510956] RSP: 0018:ffffbda3c026baf0 EFLAGS: 00010282 [ 41.511368] RAX: 0000000000000000 RBX: ffff9e9c46914800 RCX: 0000000000000000 [ 41.511910] RDX: ffff9e9c7ec29c00 RSI: ffff9e9c7ec1c900 RDI: ffff9e9c7ec1c900 [ 41.512445] RBP: ffff9e9c43660c9c R08: 0000000000009ffb R09: 00000000ffffdfff [ 41.512998] R10: 00000000ffffdfff R11: ffffffff8ca58a40 R12: ffff9e9c4339a000 [ 41.513534] R13: 0000000000000001 R14: ffff9e9c438a0000 R15: ffffbda3c026bb48 [ 41.514086] FS: 00007fbc4cda1740(0000) GS:ffff9e9c7ec00000(0000) knlGS:0000000000000000 [ 41.514726] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 41.515176] CR2: 000056233b337d88 CR3: 000000000376e006 CR4: 0000000000370ef0 [ 41.515713] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 41.516252] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 41.516799] Call Trace: [ 41.517037] [ 41.517249] ? __warn+0x7b/0x120 [ 41.517535] ? refcount_warn_saturate+0xa5/0x130 [ 41.517923] ? report_bug+0x164/0x190 [ 41.518240] ? handle_bug+0x3d/0x70 [ 41.518541] ? exc_invalid_op+0x17/0x70 [ 41.520972] ? asm_exc_invalid_op+0x1a/0x20 [ 41.521325] ? refcount_warn_saturate+0xa5/0x130 [ 41.521708] ipv6_get_ifaddr+0xda/0xe0 [ 41.522035] inet6_rtm_getaddr+0x342/0x3f0 [ 41.522376] ? __pfx_inet6_rtm_getaddr+0x10/0x10 [ 41.522758] rtnetlink_rcv_msg+0x334/0x3d0 [ 41.523102] ? netlink_unicast+0x30f/0x390 [ 41.523445] ? __pfx_rtnetlink_rcv_msg+0x10/0x10 [ 41.523832] netlink_rcv_skb+0x53/0x100 [ 41.524157] netlink_unicast+0x23b/0x390 [ 41.524484] netlink_sendmsg+0x1f2/0x440 [ 41.524826] __sys_sendto+0x1d8/0x1f0 [ 41.525145] __x64_sys_sendto+0x1f/0x30 [ 41.525467] do_syscall_64+0xa5/0x1b0 [ 41.525794] entry_SYSCALL_64_after_hwframe+0x72/0x7a [ 41.526213] RIP: 0033:0x7fbc4cfcea9a [ 41.526528] Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb b8 0f 1f 00 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 15 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 7e c3 0f 1f 44 00 00 41 54 48 83 ec 30 44 89 [ 41.527942] RSP: 002b:00007f ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.4%
EPSS %ILE
30th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

May 20, 2024

Last Modified

October 15, 2026

References (12)

Vendor Advisories for CVE-2024-35969(5)

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

Patch Availability(23)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.116.116) @ jammy2026-10-15ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.189.187) @ focal2026-10-15ubuntu
ubuntulinux-tools-nvidia-64k (6.8.0-1009.9) @ noble2026-10-15ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.189.209~18.04.1) @ bionic2026-10-15ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.116.106) @ jammy2026-10-15ubuntu
ubuntulinux-tools-azure-fde-edge (5.15.0.1068.77~20.04.1.45) @ focal2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1047 (5.4.0-1047.51) @ focal2026-10-15ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1065.65) @ jammy2026-10-15ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1065.73~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1112.142) @ focal2026-10-15ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1065.71~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-iot (5.4.0.1040.38) @ focal2026-10-15ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1008.8) @ noble2026-10-15ubuntu
ubuntulinux-tools-aws (6.8.0-1011.12) @ noble2026-10-15ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1058.56) @ jammy2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-10-15ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-38.38) @ noble2026-10-15ubuntu
redhatkernel-0:4.18.0-477.74.1.el8_82024-09-24redhat
redhatkernel-0:5.14.0-427.31.1.el9_42024-08-15redhat
redhatkernel-0:5.14.0-284.73.1.el9_22024-07-15redhat
redhatkernel-rt-0:5.14.0-284.73.1.rt14.358.el9_22024-07-15redhat
redhatkernel-0:4.18.0-372.111.1.el8_62024-07-10redhat
linuxKernel @ 4.19.313 (fixes >=2.6.35)—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

(6 across 5 ecosystems)
Debian:10(2)
PackageVulnerable rangeFix by version rangeDependents
linux4.19.118-1 ... 4.19.98-1~bpo9+1 (46 versions)
  • every version up to 4.19.316-1: fixed in 4.19.316-1
—
linux-5.105.10.136-1~deb10u1 ... 5.10.209-2~deb10u1 (13 versions)
  • every version up to 5.10.216-1~deb10u1: fixed in 5.10.216-1~deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (39 versions)
  • every version up to 5.10.216-1: fixed in 5.10.216-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.90-1~bpo11+1 (21 versions)
  • every version up to 6.1.90-1: fixed in 6.1.90-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.9-1: fixed in 6.8.9-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.9-1: fixed in 6.8.9-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(17)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× 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 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 96 of 228 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 132 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-35969?
CVE-2024-35969 is a medium-severity vulnerability; its CVE record was published on May 20, 2024. In the Linux kernel, the following vulnerability has been resolved: ipv6: fix race condition between ipv6getifaddr and ipv6deladdr Although ipv6getifaddr walks inet6addrlst under the RCU lock, it still means hlistforeachentryrcu can return an item that got removed from the list. The memory itself…
When was the CVE record for CVE-2024-35969 published?
The CVE record for CVE-2024-35969 was published on May 20, 2024. 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 15, 2026; the record at its source may have been updated since.
Is CVE-2024-35969 actively exploited?
CVE-2024-35969 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-35969?
CVE-2024-35969 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-35969?
A fix for CVE-2024-35969 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-35969 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-2024-35969

Explore →

Is Your Infrastructure Affected by CVE-2024-35969?

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

Book a Demo →Browse All CVEs