CVE-2023-52703: net/usb: kalmia: Don't pass act_len in usb_bulk_msg error path
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.25% (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 02df3170c04a8356cd571ab9155a42f030190abc, 1b5de7d44890b78519acbcc80d8d1f23ff2872e5, 338f826d3afead6e4df521f7972a4bef04a72efb.
Low priority for now. Upgrade to Linux Linux 02df3170c04a8356cd571ab9155a42f030190abc, 1b5de7d44890b78519acbcc80d8d1f23ff2872e5, 338f826d3afead6e4df521f7972a4bef04a72efb 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: net/usb: kalmia: Don't pass act_len in usb_bulk_msg error path syzbot reported that act_len in kalmia_send_init_packet() is uninitialized when passing it to the first usb_bulk_msg error path. Jiri Pirko noted that it's pointless to pass it in the error path, and that the value that would be printed in the second error path would be the value of act_len from the first call to usb_bulk_msg.[1] With this in mind, let's just not pass act_len to the usb_bulk_msg error paths. 1: https://lore.kernel.org/lkml/Y9pY61y1nwTuzMOa@nanopsycho/
- Published
- May 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- CWE-908
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Is your version affected? Check itNoroxi 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 helpAffected 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 |
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
- 3.0affected
- d40261236e8e278cb1936cb5e934262971692b10 and later · before 1b5de7d44890b78519acbcc80d8d1f23ff2872e5affected · git
- d40261236e8e278cb1936cb5e934262971692b10 and later · before 723ef7b66f37c0841f5a451ccbce47ee1641e081affected · git
- d40261236e8e278cb1936cb5e934262971692b10 and later · before a753352622b4f3c0219e0e9c73114b2848ae6042affected · git
- d40261236e8e278cb1936cb5e934262971692b10 and later · before 525bdcb0838d19d918c7786151ee14661967a030affected · git
- d40261236e8e278cb1936cb5e934262971692b10 and later · before 338f826d3afead6e4df521f7972a4bef04a72efbaffected · git
- d40261236e8e278cb1936cb5e934262971692b10 and later · before 02df3170c04a8356cd571ab9155a42f030190abcaffected · git
- d40261236e8e278cb1936cb5e934262971692b10 and later · before c68f345b7c425b38656e1791a0486769a8797016affected · git
- before 3.0not affected · semver
- 4.14.306 and later · up to and including 4.14.*not affected · semver
Affected versions · NVD (8)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.0.1 and later · before 4.14.306
- linux linux kernel4.15 and later · before 4.19.273
- linux linux kernel4.20 and later · before 5.4.232
- linux linux kernel5.5 and later · before 5.10.169
- linux linux kernel5.11 and later · before 5.15.95
- linux linux kernel5.16 and later · before 6.1.13
- linux linux kernel3.0
- linux linux kernel6.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.8.1.rt7.349.el8_10 | 4.18.0-553.8.1.rt7.349.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.8.1.rt7.349.el8_10 | 4.18.0-553.8.1.rt7.349.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.8.1.rt7.349.el8_10 | 4.18.0-553.8.1.rt7.349.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.8.1.rt7.349.el8_10 | 4.18.0-553.8.1.rt7.349.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.8.1.rt7.349.el8_10 | 4.18.0-553.8.1.rt7.349.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-kvm | before 4.18.0-553.8.1.rt7.349.el8_10 | 4.18.0-553.8.1.rt7.349.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.8.1.rt7.349.el8_10 | 4.18.0-553.8.1.rt7.349.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.8.1.rt7.349.el8_10 | 4.18.0-553.8.1.rt7.349.el8_10 |
| AlmaLinux:8 | kernel-rt-devel | before 4.18.0-553.8.1.rt7.349.el8_10 | 4.18.0-553.8.1.rt7.349.el8_10 |
| AlmaLinux:8 | kernel-rt-kvm | before 4.18.0-553.8.1.rt7.349.el8_10 | 4.18.0-553.8.1.rt7.349.el8_10 |
| AlmaLinux:8 | kernel-rt-modules | before 4.18.0-553.8.1.rt7.349.el8_10 | 4.18.0-553.8.1.rt7.349.el8_10 |
| AlmaLinux:8 | kernel-rt-modules-extra | before 4.18.0-553.8.1.rt7.349.el8_10 | 4.18.0-553.8.1.rt7.349.el8_10 |
| Debian:12 | linux | before 6.1.15-1 | 6.1.15-1 |
| Red Hat:enterprise_linux:8::nfv | kernel-rt | before 0:4.18.0-553.8.1.rt7.349.el8_10 | 0:4.18.0-553.8.1.rt7.349.el8_10 |
| Red Hat:enterprise_linux:8::nfv | kernel-rt-core | before 0:4.18.0-553.8.1.rt7.349.el8_10 | 0:4.18.0-553.8.1.rt7.349.el8_10 |
| Red Hat:enterprise_linux:8::nfv | kernel-rt-debug | before 0:4.18.0-553.8.1.rt7.349.el8_10 | 0:4.18.0-553.8.1.rt7.349.el8_10 |
| Red Hat:enterprise_linux:8::nfv | kernel-rt-debug-core | before 0:4.18.0-553.8.1.rt7.349.el8_10 | 0:4.18.0-553.8.1.rt7.349.el8_10 |
| Red Hat:enterprise_linux:8::nfv | kernel-rt-debug-debuginfo | before 0:4.18.0-553.8.1.rt7.349.el8_10 | 0:4.18.0-553.8.1.rt7.349.el8_10 |
| Red Hat:enterprise_linux:8::nfv | kernel-rt-debug-devel | before 0:4.18.0-553.8.1.rt7.349.el8_10 | 0:4.18.0-553.8.1.rt7.349.el8_10 |
| Red Hat:enterprise_linux:8::nfv | kernel-rt-debug-kvm | before 0:4.18.0-553.8.1.rt7.349.el8_10 | 0:4.18.0-553.8.1.rt7.349.el8_10 |
| Red Hat:enterprise_linux:8::nfv | kernel-rt-debug-modules | before 0:4.18.0-553.8.1.rt7.349.el8_10 | 0:4.18.0-553.8.1.rt7.349.el8_10 |
| Red Hat:enterprise_linux:8::nfv | kernel-rt-debug-modules-extra | before 0:4.18.0-553.8.1.rt7.349.el8_10 | 0:4.18.0-553.8.1.rt7.349.el8_10 |
| Red Hat:enterprise_linux:8::nfv | kernel-rt-debuginfo | before 0:4.18.0-553.8.1.rt7.349.el8_10 | 0:4.18.0-553.8.1.rt7.349.el8_10 |
| Red Hat:enterprise_linux:8::nfv | kernel-rt-debuginfo-common-x86_64 | before 0:4.18.0-553.8.1.rt7.349.el8_10 | 0:4.18.0-553.8.1.rt7.349.el8_10 |
+83
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-52701May 21, 2024 · net: use a bounce buffer for copying skb->mark28Monitor
- ← EarlierCVE-2023-52702May 21, 2024 · net: openvswitch: fix possible memory leak in ovs_meter_cmd_set()22Monitor
- Later →CVE-2023-52704May 21, 2024 · freezer,umh: Fix call_usermode_helper_exec() vs SIGKILL22Monitor
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 | 02df3170c04a8356cd571ab9155a42f030190abc | Vendor (CNA) |
| Linux Linux | 1b5de7d44890b78519acbcc80d8d1f23ff2872e5 | Vendor (CNA) |
| Linux Linux | 338f826d3afead6e4df521f7972a4bef04a72efb | Vendor (CNA) |
| Linux Linux | 525bdcb0838d19d918c7786151ee14661967a030 | Vendor (CNA) |
| Linux Linux | 723ef7b66f37c0841f5a451ccbce47ee1641e081 | Vendor (CNA) |
| Linux Linux | a753352622b4f3c0219e0e9c73114b2848ae6042 | Vendor (CNA) |
| Linux Linux | c68f345b7c425b38656e1791a0486769a8797016 | Vendor (CNA) |
| almalinux:kernel-rt | 4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-core | 4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug | 4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-core | 4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-devel | 4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-kvm | 4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-modules | 4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-modules-extra | 4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-devel | 4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-kvm | 4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-modules | 4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-modules-extra | 4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.15-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-rt | 0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-core | 0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug | 0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-core | 0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-debuginfo | 0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-devel | 0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-kvm | 0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-modules | 0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-modules-extra | 0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debuginfo | 0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
+3
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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-50302182 days apartHID: core: zero-initialize the report bufferKEV52Plan
- CVE-2024-47685153 days apartnetfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()36Monitor
- CVE-2021-475533 days apartsched/scs: Reset task stack state in bringup_cpu()31Monitor
- CVE-2024-368989 days apartgpiolib: cdev: fix uninitialised kfifo31Monitor
- CVE-2024-2702220 days apartfork: defer linking file vma until vma is fully initialized31Monitor
- CVE-2024-50143170 days apartudf: fix uninit-value use in udf_get_fileshortad31Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
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-908 · Use of Uninitialized ResourceCVSS 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
Show all references (6 more)Show less
- git.kernel.org/stable/c/1b5de7d44890b78519acbcc80d8d1f23ff2872e5
- git.kernel.org/stable/c/338f826d3afead6e4df521f7972a4bef04a72efb
- git.kernel.org/stable/c/525bdcb0838d19d918c7786151ee14661967a030
- git.kernel.org/stable/c/723ef7b66f37c0841f5a451ccbce47ee1641e081
- git.kernel.org/stable/c/a753352622b4f3c0219e0e9c73114b2848ae6042
- git.kernel.org/stable/c/c68f345b7c425b38656e1791a0486769a8797016
Vendor advisories and official records. Exploit/PoC links are deliberately left out.