CVE-2025-21812

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-02-27. NVD baseline CVSS 7.8; 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-2025-5980 (ENISA EUVD) · GHSA-5qmp-w6rv-24wf (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:

ax25: rcu protect dev->ax25_ptr

syzbot found a lockdep issue [1].

We should remove ax25 RTNL dependency in ax25_setsockopt()

This should also fix a variety of possible UAF in ax25.

[1]

WARNING: possible circular locking dependency detected 6.13.0-rc3-syzkaller-00762-g9268abe611b0 #0 Not tainted ------------------------------------------------------ syz.5.1818/12806 is trying to acquire lock: ffffffff8fcb3988 (rtnl_mutex){+.+.}-{4:4}, at: ax25_setsockopt+0xa55/0xe90 net/ax25/af_ax25.c:680

but task is already holding lock: ffff8880617ac258 (sk_lock-AF_AX25){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1618 [inline] ffff8880617ac258 (sk_lock-AF_AX25){+.+.}-{0:0}, at: ax25_setsockopt+0x209/0xe90 net/ax25/af_ax25.c:574

which lock already depends on the new lock.

the existing dependency chain (in reverse order) is:

-> #1 (sk_lock-AF_AX25){+.+.}-{0:0}: lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849 lock_sock_nested+0x48/0x100 net/core/sock.c:3642 lock_sock include/net/sock.h:1618 [inline] ax25_kill_by_device net/ax25/af_ax25.c:101 [inline] ax25_device_event+0x24d/0x580 net/ax25/af_ax25.c:146 notifier_call_chain+0x1a5/0x3f0 kernel/notifier.c:85 __dev_notify_flags+0x207/0x400 dev_change_flags+0xf0/0x1a0 net/core/dev.c:9026 dev_ifsioc+0x7c8/0xe70 net/core/dev_ioctl.c:563 dev_ioctl+0x719/0x1340 net/core/dev_ioctl.c:820 sock_do_ioctl+0x240/0x460 net/socket.c:1234 sock_ioctl+0x626/0x8e0 net/socket.c:1339 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:906 [inline] __se_sys_ioctl+0xf5/0x170 fs/ioctl.c:892 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

-> #0 (rtnl_mutex){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3904 __lock_acquire+0x1397/0x2100 kernel/locking/lockdep.c:5226 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849 __mutex_lock_common kernel/locking/mutex.c:585 [inline] __mutex_lock+0x1ac/0xee0 kernel/locking/mutex.c:735 ax25_setsockopt+0xa55/0xe90 net/ax25/af_ax25.c:680 do_sock_setsockopt+0x3af/0x720 net/socket.c:2324 __sys_setsockopt net/socket.c:2349 [inline] __do_sys_setsockopt net/socket.c:2355 [inline] __se_sys_setsockopt net/socket.c:2352 [inline] __x64_sys_setsockopt+0x1ee/0x280 net/socket.c:2352 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

other info that might help us debug this:

Possible unsafe locking scenario:

CPU0 CPU1 ---- ---- lock(sk_lock-AF_AX25); lock(rtnl_mutex); lock(sk_lock-AF_AX25); lock(rtnl_mutex);

* DEADLOCK *

1 lock held by syz.5.1818/12806: #0: ffff8880617ac258 (sk_lock-AF_AX25){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1618 [inline] #0: ffff8880617ac258 (sk_lock-AF_AX25){+.+.}-{0:0}, at: ax25_setsockopt+0x209/0xe90 net/ax25/af_ax25.c:574

stack backtrace: CPU: 1 UID: 0 PID: 12806 Comm: syz.5.1818 Not tainted 6.13.0-rc3-syzkaller-00762-g9268abe611b0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_circular_bug+0x13a/0x1b0 kernel/locking/lockdep.c:2074 check_noncircular+0x36a/0x4a0 kernel/locking/lockdep.c:2206 check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/lockin ---truncated---

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
16th
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-26). 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

February 27, 2025

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Jul 30, 2026
Patch available.
Web page

ax25: rcu protect dev->ax25_ptr - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/95fc45d1dea8e1253f8ec58abc5befb71553d666
Web page

ax25: rcu protect dev->ax25_ptr - kernel/git/stable/linux.git - Linux kernel stable tree

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

ax25: rcu protect dev->ax25_ptr - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8937f5e38a218531dce2a89fae60e3adcc2311e1
Web page

ax25: rcu protect dev->ax25_ptr - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7705d8a7f2c26c80973c81093db07c6022b2b30e
Web page

ax25: rcu protect dev->ax25_ptr - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2802ed4ced27ebd474828fc67ffd7d66f11e3605

Vendor Advisories for CVE-2025-21812(1)

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

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-aws (6.11.0-1014.15) @ oracular2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-26.26) @ oracular2026-10-27ubuntu
ubuntulinux-tools-lowlatency-hwe-24.04-edge (6.11.0-1014.15~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-64.67~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-64.67) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1025.26) @ noble2026-10-27ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-64.67.1~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1029.30) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-lts-24.04 (6.8.0-1033.35) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2026.27) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1031.35) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-nvidia-lts-24.04 (6.8.0-1022.23) @ noble2026-10-27ubuntu
linuxKernel @ 6.1.129 (fixes >=5.0.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.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
linux-6.16.1.106-3~deb11u1 ... 6.1.128-1~deb11u1 (6 versions)
  • every version up to 6.1.129-1~deb11u1: fixed in 6.1.129-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (35 versions)
  • every version up to 6.1.129-1: fixed in 6.1.129-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.13-1: fixed in 6.12.13-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.13-1: fixed in 6.12.13-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(12)

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 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 96 of 204 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 108 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-21812?
CVE-2025-21812 is a high-severity vulnerability; its CVE record was published on February 27, 2025. In the Linux kernel, the following vulnerability has been resolved: ax25: rcu protect dev->ax25_ptr syzbot found a lockdep issue [1]. We should remove ax25 RTNL dependency in ax25_setsockopt() This should also fix a variety of possible UAF in ax25. [1] WARNING: possible circular locking dependency…
When was the CVE record for CVE-2025-21812 published?
The CVE record for CVE-2025-21812 was published on February 27, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2025-21812 actively exploited?
CVE-2025-21812 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-21812?
CVE-2025-21812 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-21812?
A fix for CVE-2025-21812 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-21812 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-2025-21812

Explore →

Is Your Infrastructure Affected by CVE-2025-21812?

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

Book a Demo →Browse All CVEs