Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53426: xsk: Fix xsk_diag use-after-free error during socket cleanup

Noroxi assessment

Priority: Monitor (action score 31/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 3e019d8a05a38abb5c85d4f1e85fda964610aa14, 5.15.132, 5.17.

Low priority for now. Upgrade to Linux Linux 3e019d8a05a38abb5c85d4f1e85fda964610aa14, 5.15.132, 5.17 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: Fix xsk_diag use-after-free error during socket cleanup Fix a use-after-free error that is possible if the xsk_diag interface is used after the socket has been unbound from the device. This can happen either due to the socket being closed or the device disappearing. In the early days of AF_XDP, the way we tested that a socket was not bound to a device was to simply check if the netdevice pointer in the xsk socket structure was NULL. Later, a better system was introduced by having an explicit state variable in the xsk socket struct. For example, the state of a socket that is on the way to being closed and has been unbound from the device is XSK_UNBOUND. The commit in the Fixes tag below deleted the old way of signalling that a socket is unbound, setting dev to NULL. This in the belief that all code using the old way had been exterminated. That was unfortunately not true as the xsk diagnostics code was still using the old way and thus does not work as intended when a socket is going down. Fix this by introducing a test against the state variable. If the socket is in the state XSK_UNBOUND, simply abort the diagnostic's netlink operation.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Sep 18, 2025
Updated
Aug 5, 2026
EPSS
0.1% · 4th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Follow CVE-2023-53426

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux 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.15.132
  • linux linux kernel5.16.19 and later · before 5.17
  • linux linux kernel5.17.2 and later · before 6.1.54
  • linux linux kernel6.2 and later · before 6.5.4

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

    • d1579253ffce39986e7a6ab757ac93b2680a665f, 8a2dea162b92c322f3e42eae0c4a74b8d20aa7a9, 5.18affected
    • ad7219cd8751bd258b9d1e69ae0654ec00f71875 and later · before 5979985f2d6b565b6cf0f79a62670a2855c0e96caffected · git
    • 18b1ab7aa76bde181bdb1ab19a87fa9523c32f21 and later · before 6436973164ea5506a495f39e56be5aea375e7832affected · git
    • 18b1ab7aa76bde181bdb1ab19a87fa9523c32f21 and later · before 595931912357fa3507e522a7f8a0a76e423c23e4affected · git
    • 18b1ab7aa76bde181bdb1ab19a87fa9523c32f21 and later · before 3e019d8a05a38abb5c85d4f1e85fda964610aa14affected · git
    • 5.15.33 and later · before 5.15.132affected · semver
    • 5.16.19 and later · before 5.17affected · semver
    • 5.17.2 and later · before 5.18affected · semver
    • before 5.18not affected · semver
    • 5.15.132 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.55-16.1.55-1
Debian:13linuxbefore 6.5.6-16.5.6-1
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-develbefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-64k-debuginfobefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-64k-develbefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-debug-debuginfobefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-debug-develbefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-debuginfobefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-develbefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-devel-matchedbefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-docbefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-rt-64k-debug-debuginfobefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-rt-64k-debuginfobefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-rt-debug-debuginfobefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-rt-debuginfobefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-tools-debuginfobefore 0:5.14.0-611.5.1.el9_70:5.14.0-611.5.1.el9_7

+67

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-53424Sep 18, 2025 · clk: mediatek: fix of_iomap memory leak
    22Monitor
  • ← EarlierCVE-2023-53425Sep 18, 2025 · media: platform: mediatek: vpu: fix NULL ptr dereference
    22Monitor
  • Later →CVE-2023-53427Sep 18, 2025 · cifs: Fix warning and UAF when destroy the MR list
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3e019d8a05a38abb5c85d4f1e85fda964610aa14Vendor (CNA)
Linux Linux5.15.132Vendor (CNA)
Linux Linux5.17Vendor (CNA)
Linux Linux5.18Vendor (CNA)
Linux Linux595931912357fa3507e522a7f8a0a76e423c23e4Vendor (CNA)
Linux Linux5979985f2d6b565b6cf0f79a62670a2855c0e96cVendor (CNA)
Linux Linux6436973164ea5506a495f39e56be5aea375e7832Vendor (CNA)
debian:linux6.1.55-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-611.5.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage 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.

Finders, 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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records