CVE-2023-1073: A memory corruption flaw was found in the Linux kernel’s human interface device (HID) subsystem in how a user inserts a malicious USB device
Noroxi assessment
Priority: Monitor (action score 26/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.39% (FIRST EPSS).
- Physical access to the device is required. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: bpftool (AlmaLinux:8) 4.18.0-513.5.1.el8_9, 4.18.0-513.18.1.el8_9; kernel (AlmaLinux:8) 4.18.0-513.18.1.el8_9, 4.18.0-513.5.1.el8_9; kernel-abi-stablelists (AlmaLinux:8) 4.18.0-513.18.1.el8_9, 4.18.0-513.5.1.el8_9.
- Mentioned 3 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to bpftool (AlmaLinux:8) 4.18.0-513.5.1.el8_9, 4.18.0-513.18.1.el8_9; kernel (AlmaLinux:8) 4.18.0-513.18.1.el8_9, 4.18.0-513.5.1.el8_9; kernel-abi-stablelists (AlmaLinux:8) 4.18.0-513.18.1.el8_9, 4.18.0-513.5.1.el8_9 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
A memory corruption flaw was found in the Linux kernel’s human interface device (HID) subsystem in how a user inserts a malicious USB device. This flaw allows a local user to crash or potentially escalate their privileges on the system.
- Published
- Mar 27, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 32th percentile
- CWE
- CWE-119
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
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.
Running WordPress? Scan your site free with WP Lens
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 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 |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject fedora37
- linux linux kernelall versions
- redhat enterprise linux7.0
- redhat enterprise linux8.0
- redhat enterprise linux9.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a kernel
- unknownaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bpftool | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | bpftool | before 4.18.0-513.18.1.el8_9 | 4.18.0-513.18.1.el8_9 |
| AlmaLinux:8 | kernel | before 4.18.0-513.18.1.el8_9 | 4.18.0-513.18.1.el8_9 |
| AlmaLinux:8 | kernel | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-513.18.1.el8_9 | 4.18.0-513.18.1.el8_9 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-core | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-core | before 4.18.0-513.18.1.el8_9 | 4.18.0-513.18.1.el8_9 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-513.18.1.el8_9 | 4.18.0-513.18.1.el8_9 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-513.18.1.el8_9 | 4.18.0-513.18.1.el8_9 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-513.18.1.el8_9 | 4.18.0-513.18.1.el8_9 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-513.18.1.el8_9 | 4.18.0-513.18.1.el8_9 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-513.18.1.el8_9 | 4.18.0-513.18.1.el8_9 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-513.18.1.el8_9 | 4.18.0-513.18.1.el8_9 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-513.18.1.el8_9 | 4.18.0-513.18.1.el8_9 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-513.18.1.el8_9 | 4.18.0-513.18.1.el8_9 |
+96
Same product
linux: all recordsOther 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- 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 haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2023-28866Mar 26, 2023 · In the Linux kernel through 6.2.8, net/bluetooth/hci_sync.c allows out-of-bounds access because amp_init1[] and amp_init2[] are supposed to 21Monitor
- ← EarlierCVE-2021-3923Mar 27, 2023 · A flaw was found in the Linux kernel's implementation of RDMA over infiniband.9Monitor
- Later →CVE-2023-1074Mar 27, 2023 · A memory leak flaw was found in the Linux kernel's Stream Control Transmission Protocol.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 |
|---|---|---|
| almalinux:bpftool | 4.18.0-513.5.1.el8_9 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-513.5.1.el8_9 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-513.5.1.el8_9 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-513.5.1.el8_9 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-513.5.1.el8_9 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-513.5.1.el8_9 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-513.5.1.el8_9 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-513.5.1.el8_9 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-513.5.1.el8_9 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-513.5.1.el8_9 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-513.5.1.el8_9 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-513.5.1.el8_9 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.11-1 · Debian:12 | Package registry (OSV) |
| debian:linux-5.10 | 5.10.178-3~deb10u1 · Debian:10 | Package registry (OSV) |
| red hat:kernel-rt | 0:4.18.0-513.5.1.rt7.307.el8_9 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-core | 0:4.18.0-513.5.1.rt7.307.el8_9 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug | 0:4.18.0-513.5.1.rt7.307.el8_9 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-core | 0:4.18.0-513.5.1.rt7.307.el8_9 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-debuginfo | 0:4.18.0-513.5.1.rt7.307.el8_9 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-devel | 0:4.18.0-513.5.1.rt7.307.el8_9 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-kvm | 0:4.18.0-513.5.1.rt7.307.el8_9 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-modules | 0:4.18.0-513.5.1.rt7.307.el8_9 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-modules-extra | 0:4.18.0-513.5.1.rt7.307.el8_9 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debuginfo | 0:4.18.0-513.5.1.rt7.307.el8_9 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debuginfo-common-x86_64 | 0:4.18.0-513.5.1.rt7.307.el8_9 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-devel | 0:4.18.0-513.5.1.rt7.307.el8_9 · Red Hat:enterprise_linux:8::nfv | 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.
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.
Credits
All researchersFinders, 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0391 · Jul 10, 2023(Linux Kernel Güncellemesi)
- TR-23-0336 · Jun 9, 2023(Linux Kernel Güncellemesi)
- TR-23-0271 · May 17, 2023(Linux Kernel Güncellemesi)
Technical details
Attack conditions
- Physical access to the device is required.
- 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
- Physical
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.1/AV:P/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)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- www.openwall.com/lists/oss-security/2023/11/05/3
- bugzilla.redhat.com/show_bug.cgi?id=2173403
- git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/id=b12fece4c64857e5fab4290bf01b2e0317a88456
- lists.debian.org/debian-lts-announce/2023/05/msg00005.html
- lists.debian.org/debian-lts-announce/2023/05/msg00006.html
- www.openwall.com/lists/osssecurity/2023/01/17/3
Vendor advisories and official records. Exploit/PoC links are deliberately left out.