Skip to content
Noroxi
CVE-2025-37862· NVD / CVE Program· CNA Linux

HID: pidff: Fix null pointer dereference in pidff_find_fields

Noroxi assessment

Priority: Monitor (action score 22/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.31% (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 22a05462c3d0eee15154faf8d13c49e6295270a5, 3a507184f9307e19cb441b897c49e7843c94e56b, 44a1b8b2027afbb37e418993fb23561bdb9efb38; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1.

Low priority for now. Upgrade to Linux Linux 22a05462c3d0eee15154faf8d13c49e6295270a5, 3a507184f9307e19cb441b897c49e7843c94e56b, 44a1b8b2027afbb37e418993fb23561bdb9efb38; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1 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: HID: pidff: Fix null pointer dereference in pidff_find_fields This function triggered a null pointer dereference if used to search for a report that isn't implemented on the device. This happened both for optional and required reports alike. The same logic was applied to pidff_find_special_field and although pidff_init_fields should return an error earlier if one of the required reports is missing, future modifications could change this logic and resurface this possible null pointer dereference again. LKML bug report: https://lore.kernel.org/all/CAL-gK7f5=R0nrrQdPtaZZr1fd-cdAMbDMuZ_NLA8vM0SX+nGSw@mail.gmail.com

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 9, 2025
Updated
Jun 17, 2026
EPSS
0.3% · 22th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

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.

Follow CVE-2025-37862

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

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.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

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

  • debian debian linux11.0
  • linux linux kernel5.5 and later · before 5.10.237
  • linux linux kernel5.11 and later · before 5.15.181
  • linux linux kernel5.16 and later · before 6.1.135
  • linux linux kernelbefore 5.4.293
  • linux linux kernel6.7 and later · before 6.12.24
  • linux linux kernel6.13 and later · before 6.13.12
  • linux linux kernel6.14 and later · before 6.14.3
  • linux linux kernel6.2 and later · before 6.6.88

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

    • 2.6.19affected
    • 224ee88fe39564358ec99b46bf3ee6e6999ae17d and later · before 44a1b8b2027afbb37e418993fb23561bdb9efb38affected · git
    • 224ee88fe39564358ec99b46bf3ee6e6999ae17d and later · before d230becb9d38b7325c5c38d051693e4c26b1829baffected · git
    • 224ee88fe39564358ec99b46bf3ee6e6999ae17d and later · before 6b4449e4f03326fbd2136e67bfcc1e6ffe61541daffected · git
    • 224ee88fe39564358ec99b46bf3ee6e6999ae17d and later · before ddb147885225d768025f6818df533d30edf3e102affected · git
    • 224ee88fe39564358ec99b46bf3ee6e6999ae17d and later · before be706a48bb7896d4130edc82811233d1d62158e7affected · git
    • 224ee88fe39564358ec99b46bf3ee6e6999ae17d and later · before f8f4d77710e1c38f4a2bd26c88c4878b5b5e817aaffected · git
    • 224ee88fe39564358ec99b46bf3ee6e6999ae17d and later · before 3a507184f9307e19cb441b897c49e7843c94e56baffected · git
    • 224ee88fe39564358ec99b46bf3ee6e6999ae17d and later · before e368698da79af821f18c099520deab1219c2044baffected · git
    • 224ee88fe39564358ec99b46bf3ee6e6999ae17d and later · before 22a05462c3d0eee15154faf8d13c49e6295270a5affected · git

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.135-16.1.135-1
Debian:13linuxbefore 6.12.25-16.12.25-1

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-2025-37858May 9, 2025 · fs/jfs: Prevent integer overflow in AG size calculation
    22Monitor
  • ← EarlierCVE-2025-37859May 9, 2025 · page_pool: avoid infinite loop to schedule delayed worker
    22Monitor
  • Later →CVE-2025-37863May 9, 2025 · ovl: don't allow datadir only
    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 / packageFixed versionSource
Linux Linux22a05462c3d0eee15154faf8d13c49e6295270a5Vendor (CNA)
Linux Linux3a507184f9307e19cb441b897c49e7843c94e56bVendor (CNA)
Linux Linux44a1b8b2027afbb37e418993fb23561bdb9efb38Vendor (CNA)
Linux Linux6b4449e4f03326fbd2136e67bfcc1e6ffe61541dVendor (CNA)
Linux Linuxbe706a48bb7896d4130edc82811233d1d62158e7Vendor (CNA)
Linux Linuxd230becb9d38b7325c5c38d051693e4c26b1829bVendor (CNA)
Linux Linuxddb147885225d768025f6818df533d30edf3e102Vendor (CNA)
Linux Linuxe368698da79af821f18c099520deab1219c2044bVendor (CNA)
Linux Linuxf8f4d77710e1c38f4a2bd26c88c4878b5b5e817aVendor (CNA)
azl3 kernel 6.6.85.1-4 on Azure Linux 3.06.6.92.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.92.2-1 on Azure Linux 3.06.6.92.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.135-1 · Debian:12Package 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.

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
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

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

References

All records