CVE-2022-49204: bpf, sockmap: Fix more uncharged while msg has more_data
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.26% (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 168ff181f5b6e7fce684c98a30d35da1dbf8f82a, 244ce90c8d0bd10ebf957da02c6f3fcd5d920bdf, 7b812a369e6416ab06d83cdd39d8e3f752781dd0.
Low priority for now. Upgrade to Linux Linux 168ff181f5b6e7fce684c98a30d35da1dbf8f82a, 244ce90c8d0bd10ebf957da02c6f3fcd5d920bdf, 7b812a369e6416ab06d83cdd39d8e3f752781dd0 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: bpf, sockmap: Fix more uncharged while msg has more_data In tcp_bpf_send_verdict(), if msg has more data after tcp_bpf_sendmsg_redir(): tcp_bpf_send_verdict() tosend = msg->sg.size //msg->sg.size = 22220 case __SK_REDIRECT: sk_msg_return() //uncharged msg->sg.size(22220) sk->sk_forward_alloc tcp_bpf_sendmsg_redir() //after tcp_bpf_sendmsg_redir, msg->sg.size=11000 goto more_data; tosend = msg->sg.size //msg->sg.size = 11000 case __SK_REDIRECT: sk_msg_return() //uncharged msg->sg.size(11000) to sk->sk_forward_alloc The msg->sg.size(11000) has been uncharged twice, to fix we can charge the remaining msg->sg.size before goto more data. This issue can cause the following info: WARNING: CPU: 0 PID: 9860 at net/core/stream.c:208 sk_stream_kill_queues+0xd4/0x1a0 Call Trace: <TASK> inet_csk_destroy_sock+0x55/0x110 __tcp_close+0x279/0x470 tcp_close+0x1f/0x60 inet_release+0x3f/0x80 __sock_release+0x3d/0xb0 sock_close+0x11/0x20 __fput+0x92/0x250 task_work_run+0x6a/0xa0 do_exit+0x33b/0xb60 do_group_exit+0x2f/0xa0 get_signal+0xb6/0x950 arch_do_signal_or_restart+0xac/0x2a0 ? vfs_write+0x237/0x290 exit_to_user_mode_prepare+0xa9/0x200 syscall_exit_to_user_mode+0x12/0x30 do_syscall_64+0x46/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae </TASK> WARNING: CPU: 0 PID: 2136 at net/ipv4/af_inet.c:155 inet_sock_destruct+0x13c/0x260 Call Trace: <TASK> __sk_destruct+0x24/0x1f0 sk_psock_destroy+0x19b/0x1c0 process_one_work+0x1b3/0x3c0 worker_thread+0x30/0x350 ? process_one_work+0x3c0/0x3c0 kthread+0xe6/0x110 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30 </TASK>
- Published
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 19th percentile
- CWE
- —
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.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.
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 kernel4.20 and later · before 5.4.189
- linux linux kernel5.5 and later · before 5.10.110
- linux linux kernel5.11 and later · before 5.15.33
- linux linux kernel5.16 and later · before 5.16.19
- linux linux kernel5.17 and later · before 5.17.2
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.20affected
- 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before 244ce90c8d0bd10ebf957da02c6f3fcd5d920bdfaffected · git
- 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before 7b812a369e6416ab06d83cdd39d8e3f752781dd0affected · git
- 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before 168ff181f5b6e7fce684c98a30d35da1dbf8f82aaffected · git
- 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before 87d532d41ef937e16f61b3d2094f3a2ac49be365affected · git
- 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before abb4caa477a5450817d2aa1198edce66450aecf8affected · git
- 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before 84472b436e760ba439e1969a9e3c5ae7c86de39daffected · git
- before 4.20not affected · semver
- 5.4.189 and later · up to and including 5.4.*not affected · semver
- 5.10.110 and later · up to and including 5.10.*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 5.17.3-1 | 5.17.3-1 |
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-2022-49202Feb 26, 2025 · Bluetooth: hci_uart: add missing NULL check in h5_enqueue22Monitor
- ← EarlierCVE-2022-49203Feb 26, 2025 · drm/amd/display: Fix double free during GPU reset on DC streams22Monitor
- Later →CVE-2022-49205Feb 26, 2025 · bpf, sockmap: Fix double uncharge the mem of sk_msg31Monitor
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 | 168ff181f5b6e7fce684c98a30d35da1dbf8f82a | Vendor (CNA) |
| Linux Linux | 244ce90c8d0bd10ebf957da02c6f3fcd5d920bdf | Vendor (CNA) |
| Linux Linux | 7b812a369e6416ab06d83cdd39d8e3f752781dd0 | Vendor (CNA) |
| Linux Linux | 84472b436e760ba439e1969a9e3c5ae7c86de39d | Vendor (CNA) |
| Linux Linux | 87d532d41ef937e16f61b3d2094f3a2ac49be365 | Vendor (CNA) |
| Linux Linux | abb4caa477a5450817d2aa1198edce66450aecf8 | Vendor (CNA) |
| debian:linux | 5.17.3-1 · Debian:12 | 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)
—
CVSS 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 (5 more)Show less
- git.kernel.org/stable/c/244ce90c8d0bd10ebf957da02c6f3fcd5d920bdf
- git.kernel.org/stable/c/7b812a369e6416ab06d83cdd39d8e3f752781dd0
- git.kernel.org/stable/c/84472b436e760ba439e1969a9e3c5ae7c86de39d
- git.kernel.org/stable/c/87d532d41ef937e16f61b3d2094f3a2ac49be365
- git.kernel.org/stable/c/abb4caa477a5450817d2aa1198edce66450aecf8
Vendor advisories and official records. Exploit/PoC links are deliberately left out.