dbcve.org
Linux KernelOperating system · Linux

CVE-2022-49845

MEDIUM · 5.5 CVSS v3.1 Published 2025-05-01
Fix available
A fix is available. Upgrade to 5.4.225 / 5.10.155 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: can: j1939: j1939_send_one(): fix missing CAN header initialization The read access to struct canxl_frame::len inside of a j1939 created skbuff revealed a missing initialization of reserved and later filled elements in struct can_frame. This patch initializes the 8 byte CAN header with zero.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-908

Memory or a resource is used before it has been initialised, so its contents are whatever happened to be there — sometimes leaking earlier data, sometimes values an attacker can influence. Behaviour becomes unpredictable and occasionally exploitable. Remediation is initialising every resource before use and ensuring initialisation happens on all code paths.

General guidance for the use of uninitialized resource class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.4, < 5.4.225>= 5.5, < 5.10.155>= 5.11, < 5.15.79>= 5.16, < 6.0.9= 6.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.4.225 / 5.10.155 / 5.15.79 or later
Fixed in 5.4.2255.10.1555.15.79
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel 5.4.225 or later (for 5.4 branch), 5.10.155 or later (for 5.5-5.10 branch), 5.15.79 or later (for 5.11-5.15 branch), or 6.0.9 or later (for 5.16-6.0 branch)

  1. Identify the current running kernel version using 'uname -r' or 'cat /proc/version'
  2. Determine which version branch your current kernel belongs to (5.4.x, 5.5-5.10.x, 5.11-5.15.x, or 5.16-6.0.x)
  3. For Debian/Ubuntu-based systems: run 'sudo apt-get update' followed by 'sudo apt-get install linux-image-generic' to upgrade to the latest available kernel in your distribution's repository
  4. For RHEL/CentOS-based systems: run 'sudo yum update kernel' to install the latest kernel package
  5. For Fedora: run 'sudo dnf update kernel'
  6. After installation, reboot the system to load the new kernel
  7. Verify the fix is applied by checking 'cat /proc/version' or 'uname -a' shows a kernel version >= the fixed release for your branch
  8. Alternatively, if your distribution does not have an updated kernel package, compile from source using the stable kernel tree at https://kernel.org/ ensuring you apply commit 2719f82ad5d8199cf5f346ea8bb3998ad5323b72
Caveat Kernel upgrades may require rebuilding out-of-tree kernel modules (like proprietary drivers) and rebooting; ensure compatibility with your system applications before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-49845 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-49845 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data