dbcve.org
Linux KernelOperating system · Linux

CVE-2026-22982

MEDIUM · 5.5 CVSS v3.1 Published 2026-01-23
Fix available
A fix is available. Upgrade to 5.15.198 / 6.1.161 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: net: mscc: ocelot: Fix crash when adding interface under a lag Commit 15faa1f67ab4 ("lan966x: Fix crash when adding interface under a lag") fixed a similar issue in the lan966x driver caused by a NULL pointer dereference. The ocelot_set_aggr_pgids() function in the ocelot driver has similar logic and is susceptible to the same crash. This issue specifically affects the ocelot_vsc7514.c frontend, which leaves unused ports as NULL pointers. The felix_vsc9959.c frontend is unaffected as it uses the DSA framework which registers all ports. Fix this by checking if the port pointer is valid before accessing it.

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-476

The code follows a pointer that is null, crashing the process. An attacker who can reliably trigger it turns the crash into a denial of service. The fix is checking for null before use and handling the failure path gracefully.

General guidance for the null pointer dereference 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.12, < 5.15.198>= 5.16, < 6.1.161>= 6.2, < 6.6.121>= 6.7, < 6.12.66>= 6.13, < 6.18.6= 6.19

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.15.198 / 6.1.161 / 6.6.121 or later
Fixed in 5.15.1986.1.1616.6.121
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel 5.15.198+, 6.1.161+, 6.6.121+, or 6.12.66+ depending on your current branch

  1. Identify the currently running Linux kernel version using `uname -r`
  2. Determine which version range your current kernel falls into (5.12-5.15.197, 5.16-6.1.160, 6.2-6.6.120, or 6.7-6.12.65)
  3. Upgrade to a kernel version that includes the fix: 5.15.198 or later for 5.12-5.15.x range, 6.1.161 or later for 5.16-6.1.x range, 6.6.121 or later for 6.2-6.6.x range, or 6.12.66 or later for 6.7-6.12.x range
  4. On Debian/Ubuntu: `sudo apt-get update && sudo apt-get dist-upgrade` or install specific version via `apt-get install linux-image-<version>`
  5. On RHEL/CentOS: `sudo yum update` or `sudo dnf upgrade`
  6. On Fedora: `sudo dnf upgrade`
  7. Reboot the system to load the fixed kernel
  8. Verify the fix is applied by checking the kernel version and confirming the commit 03fb1708b7d1e76aecebf767ad059c319845039f is included
Caveat Kernel upgrades may require driver recompilation or system reboot; ensure compatibility with custom modules 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 $2,850. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22982 — 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-2026-22982 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