CVE-2026-43167

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 (severity: MODERATE) published 2026-05-06. NVD baseline CVSS 5.5; sources differ by 0.0.

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

Also known asEUVD-2026-27728 (ENISA EUVD) · GHSA-2fm8-9qc5-4mqx (GitHub Security Advisories)Source: ENISA EUVD

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.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

xfrm: always flush state and policy upon NETDEV_UNREGISTER event

syzbot is reporting that "struct xfrm_state" refcount is leaking.

unregister_netdevice: waiting for netdevsim0 to become free. Usage count = 2 ref_tracker: netdev@ffff888052f24618 has 1/1 users at __netdev_tracker_alloc include/linux/netdevice.h:4400 [inline] netdev_tracker_alloc include/linux/netdevice.h:4412 [inline] xfrm_dev_state_add+0x3a5/0x1080 net/xfrm/xfrm_device.c:316 xfrm_state_construct net/xfrm/xfrm_user.c:986 [inline] xfrm_add_sa+0x34ff/0x5fa0 net/xfrm/xfrm_user.c:1022 xfrm_user_rcv_msg+0x58e/0xc00 net/xfrm/xfrm_user.c:3507 netlink_rcv_skb+0x158/0x420 net/netlink/af_netlink.c:2550 xfrm_netlink_rcv+0x71/0x90 net/xfrm/xfrm_user.c:3529 netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline] netlink_unicast+0x5aa/0x870 net/netlink/af_netlink.c:1344 netlink_sendmsg+0x8c8/0xdd0 net/netlink/af_netlink.c:1894 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg net/socket.c:742 [inline] ____sys_sendmsg+0xa5d/0xc30 net/socket.c:2592 ___sys_sendmsg+0x134/0x1d0 net/socket.c:2646 __sys_sendmsg+0x16d/0x220 net/socket.c:2678 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f

This is because commit d77e38e612a0 ("xfrm: Add an IPsec hardware offloading API") implemented xfrm_dev_unregister() as no-op despite xfrm_dev_state_add() from xfrm_state_construct() acquires a reference to "struct net_device". I guess that that commit expected that NETDEV_DOWN event is fired before NETDEV_UNREGISTER event fires, and also assumed that xfrm_dev_state_add() is called only if (dev->features & NETIF_F_HW_ESP) != 0.

Sabrina Dubroca identified steps to reproduce the same symptoms as below.

echo 0 > /sys/bus/netdevsim/new_device dev=$(ls -1 /sys/bus/netdevsim/devices/netdevsim0/net/) ip xfrm state add src 192.168.13.1 dst 192.168.13.2 proto esp \ spi 0x1000 mode tunnel aead 'rfc4106(gcm(aes))' $key 128 \ offload crypto dev $dev dir out ethtool -K $dev esp-hw-offload off echo 0 > /sys/bus/netdevsim/del_device

Like these steps indicate, the NETIF_F_HW_ESP bit can be cleared after xfrm_dev_state_add() acquired a reference to "struct net_device". Also, xfrm_dev_state_add() does not check for the NETIF_F_HW_ESP bit when acquiring a reference to "struct net_device".

Commit 03891f820c21 ("xfrm: handle NETDEV_UNREGISTER for xfrm device") re-introduced the NETDEV_UNREGISTER event to xfrm_dev_event(), but that commit for unknown reason chose to share xfrm_dev_down() between the NETDEV_DOWN event and the NETDEV_UNREGISTER event. I guess that that commit missed the behavior in the previous paragraph.

Therefore, we need to re-introduce xfrm_dev_unregister() in order to release the reference to "struct net_device" by unconditionally flushing state and policy.

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.1% × 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.1%
EPSS %ILE
2nd
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.1% 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 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, and whom BOD 26-04 binds: 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.

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

Last Modified

November 6, 2026

Advisory Details (5)

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

xfrm: always flush state and policy upon NETDEV_UNREGISTER event - kernel/git/stable/linux.git - Linux kernel stable tree

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

xfrm: always flush state and policy upon NETDEV_UNREGISTER event - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8c75c455ecd3bfd2f36abf66edb7021c4fa19ec4
Web page

xfrm: always flush state and policy upon NETDEV_UNREGISTER event - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/59581778792cbaf8ad788f4a21dc663ce986050e
Web page

xfrm: always flush state and policy upon NETDEV_UNREGISTER event - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4efa91a28576054aae0e6dad9cba8fed8293aef8
Web page

xfrm: always flush state and policy upon NETDEV_UNREGISTER event - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/166801e49a5b5fc127b8c9e2f110f303cfddfbc3

Vendor Advisories for CVE-2026-43167(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)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)
  • every version up to 6.12.85-1: fixed in 6.12.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (117 versions)
  • every version up to 6.19.6-1: fixed in 6.19.6-1
—

All Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 9× in last 7d / 46× 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 100 of 234 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. None are among the latest 100 rows. The 134 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-43167?
CVE-2026-43167 is a medium-severity vulnerability; its CVE record was published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: xfrm: always flush state and policy upon NETDEV_UNREGISTER event syzbot is reporting that "struct xfrm_state" refcount is leaking. unregister_netdevice: waiting for netdevsim0 to become free. Usage count = 2 ref_tracker:…
When was the CVE record for CVE-2026-43167 published?
The CVE record for CVE-2026-43167 was published on May 6, 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 6, 2026; the record at its source may have been updated since.
Is CVE-2026-43167 actively exploited?
CVE-2026-43167 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-43167?
CVE-2026-43167 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43167?
A fix for CVE-2026-43167 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43167 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-43167

Explore →

Is Your Infrastructure Affected by CVE-2026-43167?

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