Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-50838: net: stream: purge sk_error_queue in sk_stream_kill_queues()

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.28% (FIRST EPSS).
  • Fixed version: Linux Linux 4.14.303, 4.19.270, 4.5.

Low priority for now. Upgrade to Linux Linux 4.14.303, 4.19.270, 4.5 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: net: stream: purge sk_error_queue in sk_stream_kill_queues() Changheon Lee reported TCP socket leaks, with a nice repro. It seems we leak TCP sockets with the following sequence: 1) SOF_TIMESTAMPING_TX_ACK is enabled on the socket. Each ACK will cook an skb put in error queue, from __skb_tstamp_tx(). __skb_tstamp_tx() is using skb_clone(), unless SOF_TIMESTAMPING_OPT_TSONLY was also requested. 2) If the application is also using MSG_ZEROCOPY, then we put in the error queue cloned skbs that had a struct ubuf_info attached to them. Whenever an struct ubuf_info is allocated, sock_zerocopy_alloc() does a sock_hold(). As long as the cloned skbs are still in sk_error_queue, socket refcount is kept elevated. 3) Application closes the socket, while error queue is not empty. Since tcp_close() no longer purges the socket error queue, we might end up with a TCP socket with at least one skb in error queue keeping the socket alive forever. This bug can be (ab)used to consume all kernel memory and freeze the host. We need to purge the error queue, with proper synchronization against concurrent writers.

—No exploit Fix available
Published
Dec 30, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 21th 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-2022-50838

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

    • 6ba975e14f5ebb87143d737c493adf4031409a68, 4437f3ead9e85c35fe0e3adfb98c0b97eaa267eb, 5.16affected
    • 7737b104c211fa843de268b897d601e070292a72 and later · before c8c1eec578a9ae2dc8f14a1846942a0b7bf29d1daffected · git
    • 89be5c357de34718eaaaefed80737f432c5ab86f and later · before bab542cf56fc174c8447c00b73be99ffd66d2d39affected · git
    • 8b8b3d738e450d2c2ccdc75f0ab5a951746c2a96 and later · before 6f00bd0402a1e3d2d556afba57c045bd7931e4d3affected · git
    • b631c603b5fb98d2bd709c35d384901965a3dd51 and later · before 4f1d37ff4226eb99d6b69e9f4518e279e1a851bfaffected · git
    • daf15fa1fd997749e881aedd9f03f73a11240e82 and later · before 9062493811676ee0efe6c74d98f00ca38c4e17d4affected · git
    • 3988164fe9ddf98ebf5b5cdede91ac38c5f08a7e and later · before 9da204cd67c4fe97e8aa465d10d5c2e7076f7f42affected · git
    • 24bcbe1cc69fa52dc4f7b5b2456678ed464724d8 and later · before 8c330c36b3970d0917f48827fa6c7a9c75aa4602affected · git
    • 24bcbe1cc69fa52dc4f7b5b2456678ed464724d8 and later · before b458d349f8753f666233828ebd30df6f100cf7d5affected · git
    • 24bcbe1cc69fa52dc4f7b5b2456678ed464724d8 and later · before e0c8bccd40fc1c19e1d246c39bcf79e357e1ada3affected · git

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.4-16.1.4-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-2022-50836Dec 30, 2025 · remoteproc: sysmon: fix memory leak in qcom_add_sysmon_subdev()
    0Monitor
  • ← EarlierCVE-2022-50837Dec 30, 2025 · net: dsa: tag_8021q: avoid leaking ctx on dsa_tag_8021q_register() error path
    0Monitor
  • Later →CVE-2022-50839Dec 30, 2025 · jbd2: fix potential buffer head reference count leak
    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 Linux4.14.303Vendor (CNA)
Linux Linux4.19.270Vendor (CNA)
Linux Linux4.5Vendor (CNA)
Linux Linux4.9.337Vendor (CNA)
Linux Linux4f1d37ff4226eb99d6b69e9f4518e279e1a851bfVendor (CNA)
Linux Linux5.10.163Vendor (CNA)
Linux Linux5.15Vendor (CNA)
Linux Linux5.15.86Vendor (CNA)
Linux Linux5.4.229Vendor (CNA)
Linux Linux6f00bd0402a1e3d2d556afba57c045bd7931e4d3Vendor (CNA)
Linux Linux8c330c36b3970d0917f48827fa6c7a9c75aa4602Vendor (CNA)
Linux Linux9062493811676ee0efe6c74d98f00ca38c4e17d4Vendor (CNA)
Linux Linux9da204cd67c4fe97e8aa465d10d5c2e7076f7f42Vendor (CNA)
Linux Linuxb458d349f8753f666233828ebd30df6f100cf7d5Vendor (CNA)
Linux Linuxbab542cf56fc174c8447c00b73be99ffd66d2d39Vendor (CNA)
Linux Linuxc8c1eec578a9ae2dc8f14a1846942a0b7bf29d1dVendor (CNA)
Linux Linuxe0c8bccd40fc1c19e1d246c39bcf79e357e1ada3Vendor (CNA)
debian:linux6.1.4-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 (8 more)

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

All records