CVE-2022-50518· NVD / CVE Program· CNA Linux

parisc: Fix locking in pdc_iodc_print() firmware call

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 04a603058e70b8b881bb7860b8bd649f931f2591, 2.6.25, 553bc5890ed96a8d006224c3a4673c47fee0d12a.

Low priority for now. Upgrade to Linux Linux 04a603058e70b8b881bb7860b8bd649f931f2591, 2.6.25, 553bc5890ed96a8d006224c3a4673c47fee0d12a or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: parisc: Fix locking in pdc_iodc_print() firmware call Utilize pdc_lock spinlock to protect parallel modifications of the iodc_dbuf[] buffer, check length to prevent buffer overflow of iodc_dbuf[], drop the iodc_retbuf[] buffer and fix some wrong indentings.

HighCVSS 7.8 · v3.1—No exploit Fix available

BDU:2025-12805

Published: Oct 7, 2025
Updated: Aug 5, 2026
EPSS: 0.1% · 2th percentile
CWE: CWE-667

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CNA vs NVD score

NVD: 7.8
CNA · Linux: 7.8; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel2.6.24.5 and later · before 2.6.25
linux linux kernel2.6.25.1 and later · before 6.0.18
linux linux kernel6.1 and later · before 6.1.4
linux linux kernel2.6.25

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 24319896af06b84f965bcefa0f2d926b726ed05b, 2.6.25affected
- ef1afd4d79f0479960ff36bb5fe6ec6eba1ebff2 and later · before 04a603058e70b8b881bb7860b8bd649f931f2591affected · git
- ef1afd4d79f0479960ff36bb5fe6ec6eba1ebff2 and later · before 553bc5890ed96a8d006224c3a4673c47fee0d12aaffected · git
- ef1afd4d79f0479960ff36bb5fe6ec6eba1ebff2 and later · before 7236aae5f81f3efbd93d0601e74fc05994bc2580affected · git
- 2.6.24.5 and later · before 2.6.25affected · semver
- before 2.6.25not affected · semver
- 6.0.18 and later · up to and including 6.0.*not affected · semver
- 6.1.4 and later · up to and including 6.1.*not affected · semver
- 6.2 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.4-1	6.1.4-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now
CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
83Now

Published before and after this one in the same product

← EarlierCVE-2022-50516Oct 7, 2025 · fs: dlm: fix invalid derefence of sb_lvbptr
22Monitor
← EarlierCVE-2022-50517Oct 7, 2025 · mm/huge_memory: do not clobber swp_entry_t during THP split
22Monitor
Later →CVE-2022-50519Oct 7, 2025 · nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	04a603058e70b8b881bb7860b8bd649f931f2591	Vendor (CNA)
Linux Linux	2.6.25	Vendor (CNA)
Linux Linux	553bc5890ed96a8d006224c3a4673c47fee0d12a	Vendor (CNA)
Linux Linux	7236aae5f81f3efbd93d0601e74fc05994bc2580	Vendor (CNA)
debian:linux	6.1.4-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Endpoint Denial of Service: Application or System ExploitationT1499.004

Change log

Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/04a603058e70b8b881bb7860b8bd649f931f2591

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records