LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49205: bpf, sockmap: Fix double uncharge the mem of sk_msg

In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix double uncharge the mem of sk_msg If tcp_bpf_sendmsg is running during a tear down operation, psock may be freed. tcp_bpf_sendmsg() tcp_bpf_send_verdict() sk_msg_return() tcp_bpf_sendmsg_redir() unlikely(!psock)) sk_msg_free() The mem of msg has been uncharged in tcp_bpf_send_verdict() by sk_msg_return(), and would be uncharged by sk_msg_free() again. When psock is null, we can simply returning an error code, this would then trigger the sk_msg_free_nocharge in the error path of __SK_REDIRECT and would have the side effect of throwing an error up to user space. This would be a slight change in behavior from user side but would look the same as an error if the redirect on the socket threw an error. This issue can cause the following info: 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>

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-49205 is a Linux kernel defect in BPF sockmap message handling. During socket teardown, memory accounting for a message can be reversed twice, producing kernel warnings and user-visible send errors. The public record does not provide a CVSS score or confirm exploitation.

Executive priority

Treat this as a kernel maintenance item unless your environment heavily uses BPF networking. No public source in the bundle confirms active exploitation or a critical impact rating, but kernel stability issues still merit timely patching.

Technical view

The issue is in tcp_bpf_sendmsg and tcp_bpf_send_verdict handling of sk_msg during psock teardown. sk_msg_return may already uncharge message memory, then sk_msg_free can uncharge it again when psock is null. Kernel stable commits change the path to return an error and use no-charge cleanup.

Likely exposure

Exposure is limited to Linux systems running affected kernel builds with BPF sockmap/sk_msg functionality reachable in their workload. The source data names Linux and lists kernel version entries, but does not give clear distribution package mappings.

Exploitation context

CISA KEV status is false in the supplied bundle, and no cited source states active exploitation. The bundle describes a race during teardown causing kernel warnings and errors, not a proven remote exploitation path.

Researcher notes

The record is source-grounded but sparse: no CVSS, CWE, exploitability analysis, or distro-specific affected ranges are provided. Focus validation on kernel lineage, whether the stable commits are present, and whether sockmap/sk_msg code paths are reachable.

Mitigation direction

  • Check your Linux distribution advisory for CVE-2022-49205 package status.
  • Update kernels to vendor-supported builds containing the referenced stable fixes.
  • Prioritize systems using BPF sockmap, service mesh, proxy, or advanced networking features.
  • Monitor kernel logs for inet_sock_destruct warnings on affected hosts.

Validation and detection

  • Inventory running kernel versions across Linux servers and containers hosts.
  • Compare installed kernel packages against vendor CVE-2022-49205 advisories.
  • Confirm whether BPF sockmap-related features are enabled or used.
  • Review kernel logs for the warning pattern cited in the CVE record.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-49205 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
7Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux604326b41a6fb9b4a78b6179335decee0365cd8c, 604326b41a6fb9b4a78b6179335decee0365cd8c, 604326b41a6fb9b4a78b6179335decee0365cd8c, 604326b41a6fb9b4a78b6179335decee0365cd8c, 604326b41a6fb9b4a78b6179335decee0365cd8c, 604326b41a6fb9b4a78b6179335decee0365cd8cunaffected
LinuxLinux4.20, 0, 5.4.189, 5.10.110, 5.15.33, 5.16.19, 5.17.2, 5.18affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.