Buffer Copy Without Checking Size of Input in Boot
Noroxi assessment
Priority: Monitor (action score 33/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.11% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
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
Memory Corruption when a corrupted ELF image with an oversized file size is read into a buffer without authentication.
- Published
- Dec 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-120
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.4
- CNA · qualcomm
- 9.0
- 0.6 point gap
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
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
- No fixed version yet
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 |
|---|---|---|
| qualcomm | qam8255p firmware | cpe:2.3:o:qualcomm:qam8255p_firmware |
| qualcomm | qam8255p | cpe:2.3:h:qualcomm:qam8255p |
| qualcomm | qam8620p firmware | cpe:2.3:o:qualcomm:qam8620p_firmware |
| qualcomm | qam8620p | cpe:2.3:h:qualcomm:qam8620p |
| qualcomm | qam8650p firmware | cpe:2.3:o:qualcomm:qam8650p_firmware |
| qualcomm | qam8650p | cpe:2.3:h:qualcomm:qam8650p |
| qualcomm | qam8775p firmware | cpe:2.3:o:qualcomm:qam8775p_firmware |
| qualcomm | qam8775p | cpe:2.3:h:qualcomm:qam8775p |
| qualcomm | qamsrv1h firmware | cpe:2.3:o:qualcomm:qamsrv1h_firmware |
| qualcomm | qamsrv1h | cpe:2.3:h:qualcomm:qamsrv1h |
| qualcomm | qamsrv1m firmware | cpe:2.3:o:qualcomm:qamsrv1m_firmware |
| qualcomm | qamsrv1m | cpe:2.3:h:qualcomm:qamsrv1m |
and 34 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm qam8255p firmwareall versions
- qualcomm qam8620p firmwareall versions
- qualcomm qam8650p firmwareall versions
- qualcomm qam8775p firmwareall versions
- qualcomm qamsrv1h firmwareall versions
- qualcomm qamsrv1m firmwareall versions
- qualcomm qca6595 firmwareall versions
- qualcomm qca6595au firmwareall versions
- qualcomm qca6678aq firmwareall versions
- qualcomm qca6696 firmwareall versions
- qualcomm qca6698aq firmwareall versions
- qualcomm qca6797aq firmwareall versions
- qualcomm sa7255p firmwareall versions
- qualcomm sa7775p firmwareall versions
- qualcomm sa8255p firmwareall versions
- qualcomm sa8620p firmwareall versions
- qualcomm sa8650p firmwareall versions
- qualcomm sa8770p firmwareall versions
- qualcomm sa8775p firmwareall versions
- qualcomm sa9000p firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (qualcomm). Independent of NVD's CPE analysis and usually ahead of it.
Qualcomm, Inc. Snapdragon
- QAM8255P, QAM8620P, QAM8650P, QAM8775P, QAMSRV1H, QAMSRV1M, QCA6595, QCA6595AU, QCA6678AQ, QCA6696, QCA6698AQ, QCA6797AQ … (+11)affected
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-53029Improper Input Validation in Automotive OS Platform35Monitor
- CVE-2024-33035Integer Overflow or Wraparound in Display33Monitor
- CVE-2025-47364Integer Overflow or Wraparound in Automotive31Monitor
- CVE-2025-47363Integer Overflow or Wraparound in Automotive31Monitor
- CVE-2025-47393Improper Validation of Array Index in Automotive Linux OS31Monitor
- CVE-2025-47365Integer Overflow or Wraparound in Automotive Platform31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
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.
No commit or PR link among the references.
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.
- CVE-2025-21444163 days apartBuffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in Data HLOS - QX31Monitor
- CVE-2025-21445163 days apartBuffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in Data HLOS - QX31Monitor
- CVE-2025-21443255 days apartBuffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in Automotive Vehicle Networks31Monitor
- CVE-2025-27072134 days apartBuffer Copy Without Checking Size of Input in Automotive Vehicle Networks22Monitor
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.
- No account or password is required.
- 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.
The bug in code
The whole CWE-120 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
char buf[256];memcpy(buf, pkt->data, pkt->len);Fixed
char buf[256];if (pkt->len > sizeof(buf)) { return -EINVAL;}memcpy(buf, pkt->data, pkt->len);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
- 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
- Overflow Variables and TagsCAPEC-46likelihood: High · High
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.