Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53825: kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg().

Noroxi assessment

Priority: Monitor (action score 0/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.25% (FIRST EPSS).
  • Fixed version: Linux Linux 1ce8362b4ac6b8e65fd04a22ea37ec776ee1ec5b, 21b467735b0888a8daa048f83d3b9b50fdab71ce, 2e18493c421428a936946c452461b8e979088f17.

Low priority for now. Upgrade to Linux Linux 1ce8362b4ac6b8e65fd04a22ea37ec776ee1ec5b, 21b467735b0888a8daa048f83d3b9b50fdab71ce, 2e18493c421428a936946c452461b8e979088f17 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: kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg(). syzkaller found a memory leak in kcm_sendmsg(), and commit c821a88bd720 ("kcm: Fix memory leak in error path of kcm_sendmsg()") suppressed it by updating kcm_tx_msg(head)->last_skb if partial data is copied so that the following sendmsg() will resume from the skb. However, we cannot know how many bytes were copied when we get the error. Thus, we could mess up the MSG_MORE queue. When kcm_sendmsg() fails for SOCK_DGRAM, we should purge the queue as we do so for UDP by udp_flush_pending_frames(). Even without this change, when the error occurred, the following sendmsg() resumed from a wrong skb and the queue was messed up. However, we have yet to get such a report, and only syzkaller stumbled on it. So, this can be changed safely. Note this does not change SOCK_SEQPACKET behaviour.

—No exploit Fix available
Published
Dec 9, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 17th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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-53825

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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.

—

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

    • 4.6affected
    • ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 and later · before 21b467735b0888a8daa048f83d3b9b50fdab71ceaffected · git
    • ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 and later · before d4b8f380b0a041ee6a84fdac14127d8fe1dcad7baffected · git
    • ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 and later · before 1ce8362b4ac6b8e65fd04a22ea37ec776ee1ec5baffected · git
    • ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 and later · before 2e18493c421428a936946c452461b8e979088f17affected · git
    • ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 and later · before 55d2e7c1ab8eaa7b62575b8a4194132795d1f9fcaffected · git
    • ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 and later · before e5b28ce127a690f3acc49a6a342e6c9442c9edd6affected · git
    • ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 and later · before 992b2ac783aad360b98ed9d4686e86176a20f6f1affected · git
    • ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 and later · before a22730b1b4bf437c6bbfdeff5feddf54be4aeadaaffected · git
    • before 4.6not 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

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-53820Dec 9, 2025 · loop: loop_set_status_from_info() check before assignment
    0Monitor
  • ← EarlierCVE-2023-53821Dec 9, 2025 · ip6_vti: fix slab-use-after-free in decode_session6
    0Monitor
  • Later →CVE-2023-53826Dec 9, 2025 · ubi: Fix UAF wear-leveling entry in eraseblk_count_seq_show()
    0Monitor

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 Linux1ce8362b4ac6b8e65fd04a22ea37ec776ee1ec5bVendor (CNA)
Linux Linux21b467735b0888a8daa048f83d3b9b50fdab71ceVendor (CNA)
Linux Linux2e18493c421428a936946c452461b8e979088f17Vendor (CNA)
Linux Linux55d2e7c1ab8eaa7b62575b8a4194132795d1f9fcVendor (CNA)
Linux Linux992b2ac783aad360b98ed9d4686e86176a20f6f1Vendor (CNA)
Linux Linuxa22730b1b4bf437c6bbfdeff5feddf54be4aeadaVendor (CNA)
Linux Linuxd4b8f380b0a041ee6a84fdac14127d8fe1dcad7bVendor (CNA)
Linux Linuxe5b28ce127a690f3acc49a6a342e6c9442c9edd6Vendor (CNA)
debian:linux6.1.55-1 · Debian:12Package 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 researchers

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

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records