Linux KernelOperating system · Linux
CVE-2022-2961
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 · uneditedA use-after-free flaw was found in the Linux kernel’s PLP Rose functionality in the way a user triggers a race condition by calling bind while simultaneously triggering the rose_bind() function. This flaw allows a local user to crash or potentially escalate their privileges on the system.
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 · moderate confidenceA use-after-free vulnerability exists in the Linux kernel's PLP Rose (Amateur Radio) networking module. The flaw is triggered by a race condition when a local user simultaneously calls bind() while rose_bind() is executing, leading to memory corruption that can cause a denial of service or privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
< 6.0= 6.0
FedoraOperating system
= 36all versionsall versionsall versionsall versionsall versionsCVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the running Linux kernel versionRun `uname -r` or check `/proc/version` to obtain the kernel versionAffected if The kernel version is less than 6.0 or equals exactly 6.0 (e.g., 5.x.y or 6.0)
-
Verify if Rose protocol support is enabled in the kernelCheck kernel config for CONFIG_NET_ROSE or look for the rose module in `/proc/modules`; also check `/proc/net/rose` existsAffected if Rose protocol module is loaded or compiled into the kernel (the vulnerable code path requires Rose socket support)
-
Identify if Rose sockets are actively used on the systemRun `netstat --protocol=rose` or check `/proc/net/rose` for active Rose sockets; also review any custom Amateur Radio configurationsAffected if Any Rose sockets exist or Rose-based services are running (the race condition triggers during bind() on Rose sockets)
-
Confirm Fedora 36 system versionCheck `/etc/fedora-release` or run `cat /etc/os-release` on Fedora-based systemsAffected if The system runs Fedora version 36 specifically (listed as affected)
-
Identify NetApp H-series hardware in useReview hardware inventory or check system documentation for NetApp H300s, H500s, H700s, H410s, or H410c modelsAffected if Any of these NetApp models are deployed (listed as affected for all firmware versions)
A system is likely affected if it runs a Linux kernel version < 6.0 or = 6.0 with Rose protocol support enabled, or uses Fedora 36, or runs on affected NetApp hardware, and actively uses Rose sockets.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data6.0
Apply the vendor-supplied Linux kernel security patch to address the race condition in the Rose socket binding code. Alternatively, upgrade to a kernel version containing the fix.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2961 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-2961 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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