CVE-2016-10142: An issue was discovered in the IPv6 protocol specification, related to ICMP Packet Too Big (PTB) messages.
Noroxi assessment
Priority: Monitor (action score 35/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: 2.8% (FIRST EPSS); higher than 86.7% of all records.
- 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.
- Fixed version: kernel (Red Hat:enterprise_linux:6::client) 0:2.6.32-696.el6; kernel-abi-whitelists (Red Hat:enterprise_linux:6::client) 0:2.6.32-696.el6; kernel-debug (Red Hat:enterprise_linux:6::client) 0:2.6.32-696.el6.
Low priority for now. Upgrade to kernel (Red Hat:enterprise_linux:6::client) 0:2.6.32-696.el6; kernel-abi-whitelists (Red Hat:enterprise_linux:6::client) 0:2.6.32-696.el6; kernel-debug (Red Hat:enterprise_linux:6::client) 0:2.6.32-696.el6 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
An issue was discovered in the IPv6 protocol specification, related to ICMP Packet Too Big (PTB) messages. (The scope of this CVE is all affected IPv6 implementations from all vendors.) The security implications of IP fragmentation have been discussed at length in [RFC6274] and [RFC7739]. An attacker can leverage the generation of IPv6 atomic fragments to trigger the use of fragmentation in an arbitrary IPv6 flow (in scenarios in which actual fragmentation of packets is not needed) and can subsequently perform any type of fragmentation-based attack against legacy IPv6 nodes that do not implement [RFC6946]. That is, employing fragmentation where not actually needed allows for fragmentation-based attack vectors to be employed, unnecessarily. We note that, unfortunately, even nodes that already implement [RFC6946] can be subject to DoS attacks as a result of the generation of IPv6 atomic fragments. Let us assume that Host A is communicating with Host B and that, as a result of the widespread dropping of IPv6 packets that contain extension headers (including fragmentation) [RFC7872], some intermediate node filters fragments between Host B and Host A. If an attacker sends a forged ICMPv6 PTB error message to Host B, reporting an MTU smaller than 1280, this will trigger the generation of IPv6 atomic fragments from that moment on (as required by [RFC2460]). When Host B starts sending IPv6 atomic fragments (in response to the received ICMPv6 PTB error message), these packets will be dropped, since we previously noted that IPv6 packets with extension headers were being dropped between Host B and Host A. Thus, this situation will result in a DoS scenario. Another possible scenario is that in which two BGP peers are employing IPv6 transport and they implement Access Control Lists (ACLs) to drop IPv6 fragments (to avoid control-plane attacks). If the aforementioned BGP peers drop IPv6 fragments but still honor received ICMPv6 PTB error messages, an attacker could easily attack the corresponding peering session by simply sending an ICMPv6 PTB message with a reported MTU smaller than 1280 bytes. Once the attack packet has been sent, the aforementioned routers will themselves be the ones dropping their own traffic.
- Published
- Jan 14, 2017
- Updated
- Jun 16, 2026
- EPSS
- 2.8% · 86th percentile
- CWE
- CWE-17
Report tools
Action score
35
Low priority for now.
- CVSS
- 34 / 40 · 8.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.8%
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 |
|---|---|---|
| ietf | ipv6 | cpe:2.3:a:ietf:ipv6 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ietf ipv6all versions
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:enterprise_linux:6::client | kernel | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::client | kernel-abi-whitelists | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::client | kernel-debug | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::client | kernel-debug-debuginfo | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::client | kernel-debug-devel | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::client | kernel-debuginfo | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::client | kernel-debuginfo-common-i686 | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::client | kernel-debuginfo-common-x86_64 | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::client | kernel-devel | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::client | kernel-doc | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::client | kernel-firmware | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::client | kernel-headers | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::client | perf | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::client | perf-debuginfo | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::client | python-perf | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::client | python-perf-debuginfo | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::server | kernel-bootwrapper | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::server | kernel-debuginfo-common-ppc64 | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::server | kernel-debuginfo-common-s390x | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::server | kernel-kdump | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::server | kernel-kdump-debuginfo | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
| Red Hat:enterprise_linux:6::server | kernel-kdump-devel | before 0:2.6.32-696.el6 | 0:2.6.32-696.el6 |
Same product
ietf: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-23019IPv6-in-IPv4 tunneling (RFC 4213) allows an attacker to spoof and route traffic via an exposed network interface.26Monitor
- CVE-2025-23018IPv4-in-IPv6 and IPv6-in-IPv6 tunneling (RFC 2473) do not require the validation or verification of the source of a network packet…26Monitor
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 |
|---|---|---|
| red hat:kernel | 0:2.6.32-696.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:kernel-abi-whitelists | 0:2.6.32-696.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:kernel-debug | 0:2.6.32-696.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:2.6.32-696.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:2.6.32-696.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:2.6.32-696.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:kernel-debuginfo-common-i686 | 0:2.6.32-696.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:kernel-debuginfo-common-x86_64 | 0:2.6.32-696.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:kernel-devel | 0:2.6.32-696.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:perf-debuginfo | 0:2.6.32-696.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:python-perf | 0:2.6.32-696.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:python-perf-debuginfo | 0:2.6.32-696.el6 · Red Hat:enterprise_linux:6::client | 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.
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-17 · DEPRECATED: CodeCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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
Vendor advisories and official records. Exploit/PoC links are deliberately left out.