LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49975: bpf: Don't redirect packets with invalid pkt_len

In the Linux kernel, the following vulnerability has been resolved: bpf: Don't redirect packets with invalid pkt_len Syzbot found an issue [1]: fq_codel_drop() try to drop a flow whitout any skbs, that is, the flow->head is null. The root cause, as the [2] says, is because that bpf_prog_test_run_skb() run a bpf prog which redirects empty skbs. So we should determine whether the length of the packet modified by bpf prog or others like bpf_prog_test is valid before forwarding it directly.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can let a BPF program redirect a packet whose length is invalid, causing kernel networking code to handle an empty packet incorrectly. The sources do not provide CVSS, exploitability, or impact details beyond the kernel bug and fix.

Executive priority

Handle through normal kernel patch governance unless critical systems rely heavily on BPF or packet processing. There is insufficient source evidence for emergency escalation, but affected kernels should not remain untracked.

Technical view

The issue is in Linux kernel BPF packet redirection. bpf_prog_test_run_skb() could run a BPF program that redirects empty skbs, leading fq_codel_drop() to process a flow without skbs. The fix validates packet length before direct forwarding.

Likely exposure

Exposure is limited to systems running affected Linux kernel versions or builds missing the listed stable commits. The source bundle does not state required privileges, reachable attack paths, or whether default configurations are exploitable.

Exploitation context

CISA KEV is false, and the supplied sources do not report active exploitation, public exploit use, or weaponized attacks. The issue was identified by syzbot testing, not by an incident report in the provided evidence.

Researcher notes

The record lacks CVSS, CWE, privilege requirements, and a precise affected-version matrix beyond kernel versions and commit identifiers. Avoid assuming local privilege escalation, remote reachability, or denial-of-service scope without kernel advisory confirmation.

Mitigation direction

  • Update Linux kernels through your distribution or stable kernel channel.
  • Confirm the fix is included or backported using the listed kernel commit references.
  • Prioritize hosts using BPF, eBPF testing, or advanced packet processing.
  • Check vendor guidance before applying local mitigations; none are named in the sources.

Validation and detection

  • Inventory running kernel versions across servers, appliances, and cloud images.
  • Compare installed kernel packages with vendor advisories and stable commit backports.
  • Review kernel changelogs for the pkt_len validation fix.
  • Run normal networking and BPF regression tests after kernel updates.
Prepared
Confidence
medium
Sources
7

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-49975 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
6Source 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
LinuxLinux5293efe62df81908f2e90c9820c7edcc8e61f5e9, 5293efe62df81908f2e90c9820c7edcc8e61f5e9, 5293efe62df81908f2e90c9820c7edcc8e61f5e9, 5293efe62df81908f2e90c9820c7edcc8e61f5e9, 5293efe62df81908f2e90c9820c7edcc8e61f5e9unaffected
LinuxLinux4.9, 0, 5.4.212, 5.10.141, 5.15.65, 5.19.7, 6.0affected
Weakness

CWE details

No CWE listed

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