CVE-2022-49497: net: remove two BUG() from skb_checksum_help()
In the Linux kernel, the following vulnerability has been resolved:
net: remove two BUG() from skb_checksum_help()
I have a syzbot report that managed to get a crash in skb_checksum_help()
If syzbot can trigger these BUG(), it makes sense to replace
them with more friendly WARN_ON_ONCE() since skb_checksum_help()
can instead return an error code.
Note that syzbot will still crash there, until real bug is fixed.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can turn a malformed local networking condition into a kernel crash, causing denial of service. It does not indicate data theft or privilege escalation in the provided sources. The main business risk is availability on systems where lower-privileged local users can exercise the vulnerable path.
Executive priority
Medium priority. Patch through the normal kernel maintenance process, with accelerated handling for systems where local users are not fully trusted or downtime would materially affect operations.
Technical view
CVE-2022-49497 concerns BUG() calls in skb_checksum_help(). A syzbot report showed these paths could be triggered and crash the kernel. The fix replaces the BUG() crashes with WARN_ON_ONCE() behavior and error handling. CVSS indicates local access, low complexity, low privileges, no user interaction, and high availability impact.
Likely exposure
Exposure is limited to affected Linux kernel versions listed by the CVE data. Systems with untrusted local users or local code execution paths have the clearest risk. The provided sources do not establish remote exploitability or affected downstream distributions.
Exploitation context
The source bundle cites syzbot-triggered crashes, not public exploitation. KEV status is false, and no cited source claims active exploitation. Treat this as a local denial-of-service risk until vendor-specific evidence says otherwise.
Researcher notes
The record’s affected-version data is broad and partially commit-based, so downstream distribution status needs vendor confirmation. The description notes syzbot may still crash until the underlying bug is fixed, making backport verification important.
Mitigation direction
Update affected Linux kernels using vendor-supported packages or stable kernel fixes.
Check vendor advisories for backported fixes before relying on version strings alone.
Prioritize shared, multi-user, and availability-critical Linux systems.
Limit local shell or workload access to trusted users where patching is delayed.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and images.
Confirm whether vendor kernels include the referenced stable commits or equivalent backports.
Review kernel logs for crashes or warnings around skb_checksum_help().
Verify monitoring detects unexpected reboots or kernel panic events.
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-49497 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.