CVE-2026-74543

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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

net: udp_tunnel: fix memory leak in udp_tunnel_nic_unregister()

syzbot reported a memory leak [1] in the UDP tunnel NIC offload code.

When device registration fails (e.g. in register_netdevice()), netdev core unwinds by sending a single NETDEV_UNREGISTER notification. If work was queued during NETDEV_REGISTER (utn->work_pending is set), udp_tunnel_nic_unregister() returns early:

if (utn->work_pending) return;

Because failed registrations do not enter netdev_wait_allrefs_any(), no subsequent NETDEV_UNREGISTER rebroadcast will ever occur. As a result, the struct udp_tunnel_nic allocated in udp_tunnel_nic_alloc() is leaked permanently.

Fix this by removing the early return. Instead, synchronously cancel any pending work with cancel_delayed_work_sync() before freeing @utn.

To be able to call cancel_delayed_work_sync() while holding RTNL (the work also needs RTNL), switch udp_tunnel_nic_device_sync_work() to rtnl_trylock(). If RTNL is contended, requeue the work with a 1 jiffy delay (via queue_delayed_work()) to prevent high CPU contention while waiting for RTNL lock.

The utn->work_pending bookkeeping is no longer needed and is removed, as the workqueue core already tracks the pending/running state of the work.

[1] BUG: memory leak unreferenced object 0xffff888127d5f840 (size 96): comm "syz-executor", pid 5806, jiffies 4294942188 backtrace (crc 99fdb6c8): __kmalloc_noprof+0x3bf/0x550 udp_tunnel_nic_alloc net/ipv4/udp_tunnel_nic.c:756 [inline] udp_tunnel_nic_register net/ipv4/udp_tunnel_nic.c:833 [inline] udp_tunnel_nic_netdevice_event+0x804/0xab0 net/ipv4/udp_tunnel_nic.c:931 notifier_call_chain+0x59/0x160 kernel/notifier.c:85 call_netdevice_notifiers_info+0x7d/0xb0 net/core/dev.c:2250 register_netdevice+0xc10/0xeb0 net/core/dev.c:11478

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Vendor Advisories for CVE-2026-74543(2)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1
  • every version up to 6.12.107-1~deb12u1: fixed in 6.12.107-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (33 versions)
  • every version up to 6.12.105-1: fixed in 6.12.105-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (165 versions)
  • every version up to 7.1.8-1: fixed in 7.1.8-1
—

Data Freshness Timeline

(refreshed 10× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-03 19:28 UTCVendor advisory
  3. 2026-10-03 19:28 UTCGHSA enrichment
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-01 19:50 UTCEPSS rescore
  6. 2026-09-30 20:55 UTCEG score recompute
  7. 2026-09-30 20:55 UTCVendor advisory
  8. 2026-09-30 20:55 UTCGHSA enrichment
  9. 2026-09-29 15:24 UTCEPSS rescore
  10. 2026-09-28 13:52 UTCEPSS rescore
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-27 08:23 UTCVendor advisory
  13. 2026-09-27 08:23 UTCGHSA enrichment
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-26 00:28 UTCEPSS rescore
  16. 2026-09-24 14:04 UTCEPSS rescore
  17. 2026-09-23 17:54 UTCEPSS rescore
  18. 2026-09-23 04:56 UTCGHSA enrichment
  19. 2026-09-22 16:01 UTCEPSS rescore
  20. 2026-09-21 21:09 UTCEPSS rescore
  21. 2026-09-20 20:16 UTCEPSS rescore
  22. 2026-09-20 09:59 UTCGHSA enrichment
  23. 2026-09-18 19:28 UTCEPSS rescore
  24. 2026-09-17 15:02 UTCGHSA enrichment
  25. 2026-09-16 14:08 UTCEPSS rescore
Show 45 more
  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-15 03:12 UTCEPSS rescore
  3. 2026-09-14 20:05 UTCGHSA enrichment
  4. 2026-09-12 15:02 UTCEPSS rescore
  5. 2026-09-11 23:50 UTCGHSA enrichment
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-10 09:35 UTCEPSS rescore
  8. 2026-09-09 03:51 UTCGHSA enrichment
  9. 2026-09-08 22:01 UTCEPSS rescore
  10. 2026-09-06 13:48 UTCEPSS rescore
  11. 2026-09-05 19:28 UTCGHSA enrichment
  12. 2026-09-04 05:07 UTCEPSS rescore
  13. 2026-09-03 00:31 UTCGHSA enrichment
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-09-01 04:40 UTCEPSS rescore
  17. 2026-09-01 04:40 UTCEPSS rescore
  18. 2026-08-31 05:10 UTCGHSA enrichment
  19. 2026-08-30 19:18 UTCEPSS rescore
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-28 21:42 UTCEPSS rescore
  22. 2026-08-28 10:13 UTCGHSA enrichment
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:47 UTCEPSS rescore
  25. 2026-08-25 15:16 UTCGHSA enrichment
  26. 2026-08-25 13:49 UTCEPSS rescore
  27. 2026-08-24 14:18 UTCEPSS rescore
  28. 2026-08-22 20:19 UTCGHSA enrichment
  29. 2026-08-21 23:49 UTCEPSS rescore
  30. 2026-08-20 22:56 UTCEPSS rescore
  31. 2026-08-20 01:22 UTCGHSA enrichment
  32. 2026-08-19 17:04 UTCEPSS rescore
  33. 2026-08-18 13:49 UTCEPSS rescore
  34. 2026-08-18 13:49 UTCEPSS rescore
  35. 2026-08-17 13:47 UTCEPSS rescore
  36. 2026-08-17 06:23 UTCGHSA enrichment
  37. 2026-08-17 06:23 UTCNVD update
  38. 2026-08-17 05:39 UTCEG score recompute
  39. 2026-08-17 05:39 UTCGHSA enrichment
  40. 2026-08-17 05:39 UTCMITRE cvelistV5
  41. 2026-08-16 14:56 UTCEPSS rescore
  42. 2026-08-16 14:56 UTCEPSS rescore
  43. 2026-08-15 13:27 UTCNVD update
  44. 2026-08-15 12:38 UTCEG score recompute
  45. 2026-08-15 12:37 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-74543?
CVE-2026-74543 is a publicly disclosed vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: net: udptunnel: fix memory leak in udptunnelnicunregister() syzbot reported a memory leak [1] in the UDP tunnel NIC offload code. When device registration fails (e.g. in register_netdevice()), netdev core unwinds by sending a…
When was CVE-2026-74543 disclosed?
CVE-2026-74543 was first published on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74543 actively exploited?
CVE-2026-74543 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-74543?
No fix for CVE-2026-74543 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-74543 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-74543

Explore →

Is Your Infrastructure Affected by CVE-2026-74543?

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