CVE-2023-53240: xsk: check IFF_UP earlier in Tx path
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1596dae2f17ec5c6e8c8f0e3fec78c5ae55c1e0b, 5.16, 5.17; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 1596dae2f17ec5c6e8c8f0e3fec78c5ae55c1e0b, 5.16, 5.17; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: xsk: check IFF_UP earlier in Tx path Xsk Tx can be triggered via either sendmsg() or poll() syscalls. These two paths share a call to common function xsk_xmit() which has two sanity checks within. A pseudo code example to show the two paths: __xsk_sendmsg() : xsk_poll(): if (unlikely(!xsk_is_bound(xs))) if (unlikely(!xsk_is_bound(xs))) return -ENXIO; return mask; if (unlikely(need_wait)) (...) return -EOPNOTSUPP; xsk_xmit() mark napi id (...) xsk_xmit() xsk_xmit(): if (unlikely(!(xs->dev->flags & IFF_UP))) return -ENETDOWN; if (unlikely(!xs->tx)) return -ENOBUFS; As it can be observed above, in sendmsg() napi id can be marked on interface that was not brought up and this causes a NULL ptr dereference: [31757.505631] BUG: kernel NULL pointer dereference, address: 0000000000000018 [31757.512710] #PF: supervisor read access in kernel mode [31757.517936] #PF: error_code(0x0000) - not-present page [31757.523149] PGD 0 P4D 0 [31757.525726] Oops: 0000 [#1] PREEMPT SMP NOPTI [31757.530154] CPU: 26 PID: 95641 Comm: xdpsock Not tainted 6.2.0-rc5+ #40 [31757.536871] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0008.031920191559 03/19/2019 [31757.547457] RIP: 0010:xsk_sendmsg+0xde/0x180 [31757.551799] Code: 00 75 a2 48 8b 00 a8 04 75 9b 84 d2 74 69 8b 85 14 01 00 00 85 c0 75 1b 48 8b 85 28 03 00 00 48 8b 80 98 00 00 00 48 8b 40 20 <8b> 40 18 89 85 14 01 00 00 8b bd 14 01 00 00 81 ff 00 01 00 00 0f [31757.570840] RSP: 0018:ffffc90034f27dc0 EFLAGS: 00010246 [31757.576143] RAX: 0000000000000000 RBX: ffffc90034f27e18 RCX: 0000000000000000 [31757.583389] RDX: 0000000000000001 RSI: ffffc90034f27e18 RDI: ffff88984cf3c100 [31757.590631] RBP: ffff88984714a800 R08: ffff88984714a800 R09: 0000000000000000 [31757.597877] R10: 0000000000000001 R11: 0000000000000000 R12: 00000000fffffffa [31757.605123] R13: 0000000000000000 R14: 0000000000000003 R15: 0000000000000000 [31757.612364] FS: 00007fb4c5931180(0000) GS:ffff88afdfa00000(0000) knlGS:0000000000000000 [31757.620571] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [31757.626406] CR2: 0000000000000018 CR3: 000000184b41c003 CR4: 00000000007706e0 [31757.633648] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [31757.640894] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [31757.648139] PKRU: 55555554 [31757.650894] Call Trace: [31757.653385] <TASK> [31757.655524] sock_sendmsg+0x8f/0xa0 [31757.659077] ? sockfd_lookup_light+0x12/0x70 [31757.663416] __sys_sendto+0xfc/0x170 [31757.667051] ? do_sched_setscheduler+0xdb/0x1b0 [31757.671658] __x64_sys_sendto+0x20/0x30 [31757.675557] do_syscall_64+0x38/0x90 [31757.679197] entry_SYSCALL_64_after_hwframe+0x72/0xdc [31757.687969] Code: 8e f6 ff 44 8b 4c 24 2c 4c 8b 44 24 20 41 89 c4 44 8b 54 24 28 48 8b 54 24 18 b8 2c 00 00 00 48 8b 74 24 10 8b 7c 24 08 0f 05 <48> 3d 00 f0 ff ff 77 3a 44 89 e7 48 89 44 24 08 e8 b5 8e f6 ff 48 [31757.707007] RSP: 002b:00007ffd49c73c70 EFLAGS: 00000293 ORIG_RAX: 000000000000002c [31757.714694] RAX: ffffffffffffffda RBX: 000055a996565380 RCX: 00007fb4c5727c16 [31757.721939] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003 [31757.729184] RBP: 0000000000000040 R08: 0000000000000000 R09: 0000000000000000 [31757.736429] R10: 0000000000000040 R11: 0000000000000293 R12: 0000000000000000 [31757.743673] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [31757.754940] </TASK> To fix this, let's make xsk_xmit a function that will be responsible for generic Tx, where RCU is handled accordingly and pull out sanity checks and xs->zc handling. Populate sanity checks to __xsk_sendmsg() and xsk_poll().
- Published
- Sep 15, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.15.33 and later · before 5.16
- linux linux kernel5.16.19 and later · before 5.17
- linux linux kernel5.17.2 and later · before 6.1.16
- linux linux kernel6.2 and later · before 6.2.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- ad7219cd8751bd258b9d1e69ae0654ec00f71875, d1579253ffce39986e7a6ab757ac93b2680a665f, 8a2dea162b92c322f3e42eae0c4a74b8d20aa7a9, 5.18affected
- 18b1ab7aa76bde181bdb1ab19a87fa9523c32f21 and later · before cecc68559cd57fffb2be50685f262b9af2318e16affected · git
- 18b1ab7aa76bde181bdb1ab19a87fa9523c32f21 and later · before ffe19750e68d0bb21e8110b398346eef20b156a7affected · git
- 18b1ab7aa76bde181bdb1ab19a87fa9523c32f21 and later · before 1596dae2f17ec5c6e8c8f0e3fec78c5ae55c1e0baffected · git
- 5.15.33 and later · before 5.16affected · semver
- 5.16.19 and later · before 5.17affected · semver
- 5.17.2 and later · before 5.18affected · semver
- before 5.18not affected · semver
- 6.1.16 and later · up to and including 6.1.*not affected · semver
- 6.2.3 and later · up to and including 6.2.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.20-1 | 6.1.20-1 |
| Red Hat:rhel_e4s:9.2::appstream | bpftool-debuginfo | before 0:7.0.0-284.154.1.el9_2 | 0:7.0.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-64k-debug-devel | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-64k-debuginfo | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-64k-devel | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-64k-devel-matched | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debug-debuginfo | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debug-devel | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debug-devel-matched | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debuginfo | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-devel | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-devel-matched | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-doc | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-tools-debuginfo | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-zfcpdump-devel | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-zfcpdump-devel-matched | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | perf | before 0:5.14.0-284.154.1.el9_2 | 0:5.14.0-284.154.1.el9_2 |
+52
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-53238Sep 15, 2025 · phy: hisilicon: Fix an out of bounds check in hisi_inno_phy_probe()28Monitor
- ← EarlierCVE-2023-53239Sep 15, 2025 · drm/msm/mdp5: Add check for kzalloc22Monitor
- Later →CVE-2023-53241Sep 15, 2025 · nfsd: call op_release, even when op_func returns an error22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1596dae2f17ec5c6e8c8f0e3fec78c5ae55c1e0b | Vendor (CNA) |
| Linux Linux | 5.16 | Vendor (CNA) |
| Linux Linux | 5.17 | Vendor (CNA) |
| Linux Linux | 5.18 | Vendor (CNA) |
| Linux Linux | cecc68559cd57fffb2be50685f262b9af2318e16 | Vendor (CNA) |
| Linux Linux | ffe19750e68d0bb21e8110b398346eef20b156a7 | Vendor (CNA) |
| cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.20-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.0.0-284.154.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-284.154.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-284.154.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-284.154.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-284.154.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-284.154.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-284.154.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-284.154.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-284.154.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-284.154.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-284.154.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-284.154.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.