CVE-2025-27071: Buffer Copy Without Checking Size of Input in Powerline Communication Firmware
Noroxi assessment
Priority: Monitor (action score 39/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.21% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
- Severity is disputed: the assigning authority (CNA) scores it 7.3, NVD 9.8.
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 while processing specific files in Powerline Communication Firmware.
- Published
- Aug 6, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-120
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.8
- CNA · qualcomm
- 7.3
- 2.5 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
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 |
|---|---|---|
| qualcomm | fastconnect 6800 firmware | cpe:2.3:o:qualcomm:fastconnect_6800_firmware |
| qualcomm | fastconnect 6800 | cpe:2.3:h:qualcomm:fastconnect_6800 |
| qualcomm | fastconnect 6900 firmware | cpe:2.3:o:qualcomm:fastconnect_6900_firmware |
| qualcomm | fastconnect 6900 | cpe:2.3:h:qualcomm:fastconnect_6900 |
| qualcomm | fastconnect 7800 firmware | cpe:2.3:o:qualcomm:fastconnect_7800_firmware |
| qualcomm | fastconnect 7800 | cpe:2.3:h:qualcomm:fastconnect_7800 |
| qualcomm | qca6391 firmware | cpe:2.3:o:qualcomm:qca6391_firmware |
| qualcomm | qca6391 | cpe:2.3:h:qualcomm:qca6391 |
| qualcomm | qca6426 firmware | cpe:2.3:o:qualcomm:qca6426_firmware |
| qualcomm | qca6426 | cpe:2.3:h:qualcomm:qca6426 |
| qualcomm | qca6436 firmware | cpe:2.3:o:qualcomm:qca6436_firmware |
| qualcomm | qca6436 | cpe:2.3:h:qualcomm:qca6436 |
and 56 more
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
- FastConnect 6800, FastConnect 6900, FastConnect 7800, QCA6391, QCA6426, QCA6436, QSM8250, SD865 5G, SDM429W, SDX55, Snapdragon 429 Mobile Platform, Snapdragon 8 Gen 1 Mobile Platform … (+22)affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm fastconnect 6800 firmwareall versions
- qualcomm fastconnect 6900 firmwareall versions
- qualcomm fastconnect 7800 firmwareall versions
- qualcomm qca6391 firmwareall versions
- qualcomm qca6426 firmwareall versions
- qualcomm qca6436 firmwareall versions
- qualcomm qsm8250 firmwareall versions
- qualcomm sd865 5g firmwareall versions
- qualcomm sdm429w firmwareall versions
- qualcomm sdx55 firmwareall versions
- qualcomm snapdragon 429 mobile platform firmwareall versions
- qualcomm snapdragon 8 gen 1 mobile platform firmwareall versions
- qualcomm snapdragon 865 5g mobile platform firmwareall versions
- qualcomm snapdragon 865+ 5g mobile platform (sm8250-ab) firmwareall versions
- qualcomm snapdragon 870 5g mobile platform (sm8250-ac) firmwareall versions
- qualcomm snapdragon w5+ gen 1 wearable platform firmwareall versions
- qualcomm snapdragon x55 5g modem-rf system firmwareall versions
- qualcomm snapdragon xr2 5g platform firmwareall versions
- qualcomm sw5100 firmwareall versions
- qualcomm sw5100p firmwareall versions
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-28581Improper Restriction of Operations within the Bounds of a Memory Buffer in WLAN Firmware39Monitor
- CVE-2025-27037Use After Free in Camera Driver31Monitor
- CVE-2025-21474Use After Free in BTHOST31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-45566May 6, 2025 · Use After Free in Camera Driver31Monitor
- ← EarlierCVE-2024-53016Jun 3, 2025 · Time-of-check Time-of-use (TOCTOU) Race Condition in Camera Driver26Monitor
- ← EarlierCVE-2025-21455Aug 6, 2025 · Time-of-check Time-of-use (TOCTOU) Race Condition in Camera_Linux31Monitor
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet 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
- Network
- 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:N/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 (0)
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.