CVE-2026-23343

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 2026-03-25. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-15310 (ENISA EUVD) · GHSA-rqf2-6q66-wgpp (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.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

xdp: produce a warning when calculated tailroom is negative

Many ethernet drivers report xdp Rx queue frag size as being the same as DMA write size. However, the only user of this field, namely bpf_xdp_frags_increase_tail(), clearly expects a truesize.

Such difference leads to unspecific memory corruption issues under certain circumstances, e.g. in ixgbevf maximum DMA write size is 3 KB, so when running xskxceiver's XDP_ADJUST_TAIL_GROW_MULTI_BUFF, 6K packet fully uses all DMA-writable space in 2 buffers. This would be fine, if only rxq->frag_size was properly set to 4K, but value of 3K results in a negative tailroom, because there is a non-zero page offset.

We are supposed to return -EINVAL and be done with it in such case, but due to tailroom being stored as an unsigned int, it is reported to be somewhere near UINT_MAX, resulting in a tail being grown, even if the requested offset is too much (it is around 2K in the abovementioned test). This later leads to all kinds of unspecific calltraces.

[ 7340.337579] xskxceiver[1440]: segfault at 1da718 ip 00007f4161aeac9d sp 00007f41615a6a00 error 6 [ 7340.338040] xskxceiver[1441]: segfault at 7f410000000b ip 00000000004042b5 sp 00007f415bffecf0 error 4 [ 7340.338179] in libc.so.6[61c9d,7f4161aaf000+160000] [ 7340.339230] in xskxceiver[42b5,400000+69000] [ 7340.340300] likely on CPU 6 (core 0, socket 6) [ 7340.340302] Code: ff ff 01 e9 f4 fe ff ff 0f 1f 44 00 00 4c 39 f0 74 73 31 c0 ba 01 00 00 00 f0 0f b1 17 0f 85 ba 00 00 00 49 8b 87 88 00 00 00 <4c> 89 70 08 eb cc 0f 1f 44 00 00 48 8d bd f0 fe ff ff 89 85 ec fe [ 7340.340888] likely on CPU 3 (core 0, socket 3) [ 7340.345088] Code: 00 00 00 ba 00 00 00 00 be 00 00 00 00 89 c7 e8 31 ca ff ff 89 45 ec 8b 45 ec 85 c0 78 07 b8 00 00 00 00 eb 46 e8 0b c8 ff ff <8b> 00 83 f8 69 74 24 e8 ff c7 ff ff 8b 00 83 f8 0b 74 18 e8 f3 c7 [ 7340.404334] Oops: general protection fault, probably for non-canonical address 0x6d255010bdffc: 0000 [#1] SMP NOPTI [ 7340.405972] CPU: 7 UID: 0 PID: 1439 Comm: xskxceiver Not tainted 6.19.0-rc1+ #21 PREEMPT(lazy) [ 7340.408006] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014 [ 7340.409716] RIP: 0010:lookup_swap_cgroup_id+0x44/0x80 [ 7340.410455] Code: 83 f8 1c 73 39 48 ba ff ff ff ff ff ff ff 03 48 8b 04 c5 20 55 fa bd 48 21 d1 48 89 ca 83 e1 01 48 d1 ea c1 e1 04 48 8d 04 90 <8b> 00 48 83 c4 10 d3 e8 c3 cc cc cc cc 31 c0 e9 98 b7 dd 00 48 89 [ 7340.412787] RSP: 0018:ffffcc5c04f7f6d0 EFLAGS: 00010202 [ 7340.413494] RAX: 0006d255010bdffc RBX: ffff891f477895a8 RCX: 0000000000000010 [ 7340.414431] RDX: 0001c17e3fffffff RSI: 00fa070000000000 RDI: 000382fc7fffffff [ 7340.415354] RBP: 00fa070000000000 R08: ffffcc5c04f7f8f8 R09: ffffcc5c04f7f7d0 [ 7340.416283] R10: ffff891f4c1a7000 R11: ffffcc5c04f7f9c8 R12: ffffcc5c04f7f7d0 [ 7340.417218] R13: 03ffffffffffffff R14: 00fa06fffffffe00 R15: ffff891f47789500 [ 7340.418229] FS: 0000000000000000(0000) GS:ffff891ffdfaa000(0000) knlGS:0000000000000000 [ 7340.419489] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 7340.420286] CR2: 00007f415bfffd58 CR3: 0000000103f03002 CR4: 0000000000772ef0 [ 7340.421237] PKRU: 55555554 [ 7340.421623] Call Trace: [ 7340.421987] [ 7340.422309] ? softleaf_from_pte+0x77/0xa0 [ 7340.422855] swap_pte_batch+0xa7/0x290 [ 7340.423363] zap_nonpresent_ptes.constprop.0.isra.0+0xd1/0x270 [ 7340.424102] zap_pte_range+0x281/0x580 [ 7340.424607] zap_pmd_range.isra.0+0xc9/0x240 [ 7340.425177] unmap_page_range+0x24d/0x420 [ 7340.425714] unmap_vmas+0xa1/0x180 [ 7340.426185] exit_mmap+0xe1/0x3b0 [ 7340.426644] __mmput+0x41/0x150 [ 7340.427098] exit_mm+0xb1/0x110 [ 7340.427539] do_exit+0x1b2/0x460 [ 7340.427992] do_group_exit+0x2d/0xc0 [ 7340.428477] get_signal+0x79d/0x7e0 [ 7340.428957] arch_do_signal_or_restart+0x34/0x100 [ 7340.429571] exit_to_user_mode_loop+0x8e/0x4c0 [ 7340.430159] do_syscall_64+0x188/ ---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.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
3rd
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.1% 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 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

March 25, 2026

Last Modified

November 10, 2026

Advisory Details (6)

Auto-updated Jun 10, 2026
Patch available.
Web page

xdp: produce a warning when calculated tailroom is negative - kernel/git/stable/linux.git - Linux kernel stable tree

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

xdp: produce a warning when calculated tailroom is negative - kernel/git/stable/linux.git - Linux kernel stable tree

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

xdp: produce a warning when calculated tailroom is negative - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98cd8b4d0b836d3edf70161f40efd9cbb8c8f252
Web page

xdp: produce a warning when calculated tailroom is negative - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/94b9da7e9f958cb3d115b21eff824ecd8c3217aa
Web page

xdp: produce a warning when calculated tailroom is negative - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8821e857759be9db3cde337ad328b71fe5c8a55f
Web page

xdp: produce a warning when calculated tailroom is negative - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/01379540452a02bbc52f639d45dd365cd3624efb

Vendor Advisories for CVE-2026-23343(2)

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

Patch Availability(15)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-10-29ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-10-29ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-29ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-10-29ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-29ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-10-29ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-10-29ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-10-29ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-10-29ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-10-29ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-10-29ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-10-29ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-29ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-29ubuntu
linuxKernel @ 6.1.167 (fixes >=5.18.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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)
  • every version up to 6.1.170-1~deb11u1: fixed in 6.1.170-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)
  • every version up to 6.1.170-1: fixed in 6.1.170-1
—
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 (124 versions)
  • every version up to 6.19.8-1: fixed in 6.19.8-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(14)

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 / 42× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 303 rows on record for this CVE, as 99 entries (1 repeat merged).

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 203 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-23343?
CVE-2026-23343 is a high-severity vulnerability; its CVE record was published on March 25, 2026. In the Linux kernel, the following vulnerability has been resolved: xdp: produce a warning when calculated tailroom is negative Many ethernet drivers report xdp Rx queue frag size as being the same as DMA write size. However, the only user of this field, namely bpf_xdp_frags_increase_tail(),…
When was the CVE record for CVE-2026-23343 published?
The CVE record for CVE-2026-23343 was published on March 25, 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 10, 2026; the record at its source may have been updated since.
Is CVE-2026-23343 actively exploited?
CVE-2026-23343 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-23343?
CVE-2026-23343 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-23343?
A fix for CVE-2026-23343 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-23343 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-23343

Explore →

Is Your Infrastructure Affected by CVE-2026-23343?

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

Book a Demo →Browse All CVEs