dbcve.org
Linux KernelOperating system · Linux

CVE-2022-48711

MEDIUM · 5.5 CVSS v3.1 Published 2024-06-20
Fix available
A fix is available. Upgrade to 4.9.301 / 4.14.266 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: tipc: improve size validations for received domain records The function tipc_mon_rcv() allows a node to receive and process domain_record structs from peer nodes to track their views of the network topology. This patch verifies that the number of members in a received domain record does not exceed the limit defined by MAX_MON_DOMAIN, something that may otherwise lead to a stack overflow. tipc_mon_rcv() is called from the function tipc_link_proto_rcv(), where we are reading a 32 bit message data length field into a uint16. To avert any risk of bit overflow, we add an extra sanity check for this in that function. We cannot see that happen with the current code, but future designers being unaware of this risk, may introduce it by allowing delivery of very large (> 64k) sk buffers from the bearer layer. This potential problem was identified by Eric Dumazet. This fixes CVE-2022-0435

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

The program writes past the bounds of a buffer, overwriting adjacent memory an attacker can turn to their advantage. Crafted input can overwrite control data and redirect execution. Remediation is validating every index and length before a write, plus modern memory-safety mitigations.

General guidance for the out-of-bounds write 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:>= 4.8, < 4.9.301>= 4.10, < 4.14.266>= 4.15, < 4.19.229>= 4.20, < 5.4.179>= 5.5, < 5.10.100>= 5.11, < 5.15.23>= 5.16, < 5.16.9= 5.17

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.9.301 / 4.14.266 / 4.19.229 or later
Fixed in 4.9.3014.14.2664.19.229
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel 4.9.301+/4.14.266+/4.19.229+/5.4.179+ (preferably 5.4.238+ or newer stable release)

  1. 1. Identify the currently running kernel version using `uname -r`
  2. 2. Determine which kernel branch your current version belongs to (4.9.x, 4.14.x, 4.19.x, or 5.4.x)
  3. 3. For 4.9.x branch: upgrade to kernel version 4.9.301 or later
  4. 4. For 4.14.x branch: upgrade to kernel version 4.14.266 or later
  5. 5. For 4.19.x branch: upgrade to kernel version 4.19.229 or later
  6. 6. For 5.4.x branch: upgrade to kernel version 5.4.179 or later
  7. 7. Alternatively, upgrade to a newer stable release such as 5.4.238+ or 5.10+ for the most complete fix
  8. 8. After kernel upgrade, reboot the system to load the fixed kernel
Caveat Kernel upgrades may require rebuilding out-of-tree kernel modules; ensure compatibility of hardware drivers and third-party modules with the new kernel version

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-2022-48711 — 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-48711 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