Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-22003: can: ucan: fix out of bound read in strscpy() source

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.19% (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 1d22a122ffb116c3cf78053e812b8b21f8852ee9, 8cec9e314d3360fc1d8346297c41a6ee45cb45a9, a4994161a61bc8fd71d105c579d847cefee99262; azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 6.6.85.1-2; azl3 kernel 6.6.85.1-2 on Azure Linux 3.0 6.6.85.1-2.

Low priority for now. Upgrade to Linux Linux 1d22a122ffb116c3cf78053e812b8b21f8852ee9, 8cec9e314d3360fc1d8346297c41a6ee45cb45a9, a4994161a61bc8fd71d105c579d847cefee99262; azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 6.6.85.1-2; azl3 kernel 6.6.85.1-2 on Azure Linux 3.0 6.6.85.1-2 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: can: ucan: fix out of bound read in strscpy() source Commit 7fdaf8966aae ("can: ucan: use strscpy() to instead of strncpy()") unintentionally introduced a one byte out of bound read on strscpy()'s source argument (which is kind of ironic knowing that strscpy() is meant to be a more secure alternative :)). Let's consider below buffers: dest[len + 1]; /* will be NUL terminated */ src[len]; /* may not be NUL terminated */ When doing: strncpy(dest, src, len); dest[len] = '\0'; strncpy() will read up to len bytes from src. On the other hand: strscpy(dest, src, len + 1); will read up to len + 1 bytes from src, that is to say, an out of bound read of one byte will occur on src if it is not NUL terminated. Note that the src[len] byte is never copied, but strscpy() still needs to read it to check whether a truncation occurred or not. This exact pattern happened in ucan. The root cause is that the source is not NUL terminated. Instead of doing a copy in a local buffer, directly NUL terminate it as soon as usb_control_msg() returns. With this, the local firmware_str[] variable can be removed. On top of this do a couple refactors: - ucan_ctl_payload->raw is only used for the firmware string, so rename it to ucan_ctl_payload->fw_str and change its type from u8 to char. - ucan_device_request_in() is only used to retrieve the firmware string, so rename it to ucan_get_fw_str() and refactor it to make it directly handle all the string termination logic.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Apr 3, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 8th 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.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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

Affected versions

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

  • linux linux kernel6.2 and later · before 6.6.85
  • linux linux kernel6.7 and later · before 6.12.21
  • linux linux kernel6.13 and later · before 6.13.9
  • linux linux kernel6.14

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

    • 6.2affected
    • 7fdaf8966aae476deafe11f9a0067ff588615444 and later · before cc29775a8a72d7f3b56cc026796ad99bd65804a7affected · git
    • 7fdaf8966aae476deafe11f9a0067ff588615444 and later · before 8cec9e314d3360fc1d8346297c41a6ee45cb45a9affected · git
    • 7fdaf8966aae476deafe11f9a0067ff588615444 and later · before a4994161a61bc8fd71d105c579d847cefee99262affected · git
    • 7fdaf8966aae476deafe11f9a0067ff588615444 and later · before 1d22a122ffb116c3cf78053e812b8b21f8852ee9affected · git
    • before 6.2not affected · semver
    • 6.6.85 and later · up to and including 6.6.*not affected · semver
    • 6.12.21 and later · up to and including 6.12.*not affected · semver
    • 6.13.9 and later · up to and including 6.13.*not affected · semver
    • 6.14 and laternot affected · original_commit_for_fix

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.21-16.12.21-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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

Published before and after this one in the same product

  • ← EarlierCVE-2025-22001Apr 3, 2025 · accel/qaic: Fix integer overflow in qaic_validate_req()
    22Monitor
  • ← EarlierCVE-2025-22002Apr 3, 2025 · netfs: Call `invalidate_cache` only if implemented
    22Monitor
  • Later →CVE-2025-22004Apr 3, 2025 · net: atm: fix use after free in lec_send()
    34Monitor

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 Linux1d22a122ffb116c3cf78053e812b8b21f8852ee9Vendor (CNA)
Linux Linux8cec9e314d3360fc1d8346297c41a6ee45cb45a9Vendor (CNA)
Linux Linuxa4994161a61bc8fd71d105c579d847cefee99262Vendor (CNA)
Linux Linuxcc29775a8a72d7f3b56cc026796ad99bd65804a7Vendor (CNA)
azl3 kernel 6.6.82.1-1 on Azure Linux 3.06.6.85.1-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.85.1-2 on Azure Linux 3.06.6.85.1-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.12.21-1 · Debian:13Package 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.

No history yet (it accumulates with the daily EPSS job).

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

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

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.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

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

References

Show all references (3 more)

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

All records