dbcve.org
Linux KernelOperating system · Linux

CVE-2022-49367

MEDIUM · 5.5 CVSS v3.1 Published 2025-02-26
Fix available
A fix is available. Upgrade to 4.14.283 / 4.19.247 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: dsa: mv88e6xxx: Fix refcount leak in mv88e6xxx_mdios_register of_get_child_by_name() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. mv88e6xxx_mdio_register() pass the device node to of_mdiobus_register(). We don't need the device node after it. Add missing of_node_put() to avoid refcount leak.

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

A detailed technical summary for this CVE is being prepared.

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:>= 4.11, < 4.14.283>= 4.15, < 4.19.247>= 4.20, < 5.4.198>= 5.5, < 5.10.122>= 5.11, < 5.15.47>= 5.16, < 5.17.15>= 5.18, < 5.18.4

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 4.14.283 / 4.19.247 / 5.4.198 or later
Fixed in 4.14.2834.19.2475.4.198
Vendor patch git.kernel.org →
Recommended fix High confidence

Linux kernel 4.14.283, 4.19.247, 5.4.198, or 5.10.122 or later (minimum fixed version depends on the branch: 4.14.x requires >=4.14.283, 4.19.x requires >=4.19.247, 5.4.x requires >=5.4.198, 5.10.x requires >=5.10.122)

  1. Identify the affected Linux kernel version using 'uname -r' or checking /proc/version
  2. Apply the vendor patch commit 02ded5a173619b11728b8bf75a3fd995a2c1ff28 which adds the missing of_node_put() call in the mv88e6xxx_mdios_register function in drivers/net/dsa/mv88e6xxx/mv88e6xxx_mdio.c
  3. Alternatively, upgrade the kernel to a fixed release version (see upgrade_path)
  4. Reboot the system to load the fixed kernel
  5. Verify the fix is applied by checking the mv88e6xxx driver code for the added of_node_put() call or by confirming the kernel version
Caveat Kernel upgrades may introduce regressions; test in staging environment first. The fix is a simple one-line addition of of_node_put() so applying just the patch is lower risk than a full kernel upgrade.

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-49367 — 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-49367 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