CVE-2024-56635

HIGHNVD 7.07.0
EchelonGraph scoreMEDIUM confidence

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

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2024-12-27. NVD baseline CVSS 7.0; sources differ by 0.0.

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

Also known asEUVD-2024-53283 (ENISA EUVD) · GHSA-m2h6-g9h7-jxfj (GitHub Security Advisories)Source: ENISA EUVD

7.0EG
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.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net: avoid potential UAF in default_operstate()

syzbot reported an UAF in default_operstate() [1]

Issue is a race between device and netns dismantles.

After calling __rtnl_unlock() from netdev_run_todo(), we can not assume the netns of each device is still alive.

Make sure the device is not in NETREG_UNREGISTERED state, and add an ASSERT_RTNL() before the call to __dev_get_by_index().

We might move this ASSERT_RTNL() in __dev_get_by_index() in the future.

[1]

BUG: KASAN: slab-use-after-free in __dev_get_by_index+0x5d/0x110 net/core/dev.c:852 Read of size 8 at addr ffff888043eba1b0 by task syz.0.0/5339

CPU: 0 UID: 0 PID: 5339 Comm: syz.0.0 Not tainted 6.12.0-syzkaller-10296-gaaf20f870da0 #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0x169/0x550 mm/kasan/report.c:489 kasan_report+0x143/0x180 mm/kasan/report.c:602 __dev_get_by_index+0x5d/0x110 net/core/dev.c:852 default_operstate net/core/link_watch.c:51 [inline] rfc2863_policy+0x224/0x300 net/core/link_watch.c:67 linkwatch_do_dev+0x3e/0x170 net/core/link_watch.c:170 netdev_run_todo+0x461/0x1000 net/core/dev.c:10894 rtnl_unlock net/core/rtnetlink.c:152 [inline] rtnl_net_unlock include/linux/rtnetlink.h:133 [inline] rtnl_dellink+0x760/0x8d0 net/core/rtnetlink.c:3520 rtnetlink_rcv_msg+0x791/0xcf0 net/core/rtnetlink.c:6911 netlink_rcv_skb+0x1e3/0x430 net/netlink/af_netlink.c:2541 netlink_unicast_kernel net/netlink/af_netlink.c:1321 [inline] netlink_unicast+0x7f6/0x990 net/netlink/af_netlink.c:1347 netlink_sendmsg+0x8e4/0xcb0 net/netlink/af_netlink.c:1891 sock_sendmsg_nosec net/socket.c:711 [inline] __sock_sendmsg+0x221/0x270 net/socket.c:726 ____sys_sendmsg+0x52a/0x7e0 net/socket.c:2583 ___sys_sendmsg net/socket.c:2637 [inline] __sys_sendmsg+0x269/0x350 net/socket.c:2669 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f2a3cb80809 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f2a3d9cd058 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f2a3cd45fa0 RCX: 00007f2a3cb80809 RDX: 0000000000000000 RSI: 0000000020000000 RDI: 0000000000000008 RBP: 00007f2a3cbf393e R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f2a3cd45fa0 R15: 00007ffd03bc65c8

Allocated by task 5339: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:377 [inline] __kasan_kmalloc+0x98/0xb0 mm/kasan/common.c:394 kasan_kmalloc include/linux/kasan.h:260 [inline] __kmalloc_cache_noprof+0x243/0x390 mm/slub.c:4314 kmalloc_noprof include/linux/slab.h:901 [inline] kmalloc_array_noprof include/linux/slab.h:945 [inline] netdev_create_hash net/core/dev.c:11870 [inline] netdev_init+0x10c/0x250 net/core/dev.c:11890 ops_init+0x31e/0x590 net/core/net_namespace.c:138 setup_net+0x287/0x9e0 net/core/net_namespace.c:362 copy_net_ns+0x33f/0x570 net/core/net_namespace.c:500 create_new_namespaces+0x425/0x7b0 kernel/nsproxy.c:110 unshare_nsproxy_namespaces+0x124/0x180 kernel/nsproxy.c:228 ksys_unshare+0x57d/0xa70 kernel/fork.c:3314 __do_sys_unshare kernel/fork.c:3385 [inline] __se_sys_unshare kernel/fork.c:3383 [inline] __x64_sys_unshare+0x38/0x40 kernel/fork.c:3383 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x8 ---truncated---

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity70% × 45%
Impact severity (EG Severity): CVSS 7.0 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
8th
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.0): severity, escalated by confirmed exploitation. This CVE's 7.0 is its impact severity (EG Severity), not escalated.

EG Severity
7.0 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. 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 (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.

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

December 27, 2024

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 5, 2026
Patch available.
Web page

net: avoid potential UAF in default_operstate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/750e51603395e755537da08f745864c93e3ce741
Web page

net: avoid potential UAF in default_operstate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/316183d58319f191e16503bc2dffa156c4442df2
Web page

net: avoid potential UAF in default_operstate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3265aab0736f78bb218200b06b1abb525c316269

Vendor Advisories for CVE-2024-56635(1)

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

Patch Availability(15)

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
linux—
  • every version up to 6.12.5-1: fixed in 6.12.5-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.5-1: fixed in 6.12.5-1
—

Weakness Classification(2)

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

Additional Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 218 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 123 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-56635?
CVE-2024-56635 is a high-severity vulnerability; its CVE record was published on December 27, 2024. In the Linux kernel, the following vulnerability has been resolved: net: avoid potential UAF in default_operstate() syzbot reported an UAF in default_operstate() [1] Issue is a race between device and netns dismantles. After calling __rtnl_unlock() from netdev_run_todo(), we can not assume the…
When was the CVE record for CVE-2024-56635 published?
The CVE record for CVE-2024-56635 was published on December 27, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-56635 actively exploited?
CVE-2024-56635 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-56635?
CVE-2024-56635 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2024-56635?
A fix for CVE-2024-56635 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-56635 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-56635

Explore →

Is Your Infrastructure Affected by CVE-2024-56635?

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