CVE-2019-10639: Weak Encryption

Published Jul 5, 2019
·
Updated

A flaw was found in the way the Linux kernel derived the IP ID field from a partial kernel space address returned by a nethashmix() function. A remote user could observe this IP ID field to extract the kernel address bits used to derive its value, which may result in leaking the hash key and potentially defeating KASLR.

Other sources

Linux Kernel could allow a remote attacker to obtain sensitive information, caused by the use of a weak function to generate IP packet IDs. By sniffing the network, an attacker could exploit this vulnerability to obtain hash collisions information to derive the hashing key.

IBM

The Linux kernel 4.x (starting from 4.1) and 5.x before 5.0.8 allows Information Exposure (partial kernel address disclosure), leading to a KASLR bypass. Specifically, it is possible to extract the KASLR kernel image offset using the IP ID values the kernel produces for connection-less protocols (e.g., UDP and ICMP). When such traffic is sent to multiple destination IP addresses, it is possible to obtain hash collisions (of indices to the counter array) and thereby obtain the hashing key (via enumeration). This key contains enough bits from a kernel address (of a static variable) so when the key is extracted (via enumeration), the offset of the kernel image is exposed. This attack can be carried out remotely, by the attacker forcing the target device to send UDP or ICMP (or certain other) traffic to attacker-controlled IP addresses. Forcing a server to send UDP traffic is trivial if the server is a DNS server. ICMP traffic is trivial if the server answers ICMP Echo requests (ping). For client targets, if the target visits the attacker's web page, then WebRTC or gQUIC can be used to force UDP traffic to attacker-controlled IP addresses. NOTE: this attack against KASLR became viable in 4.1 because IP ID generation was changed to have a dependency on an address associated with a network namespace.

When IP packet fragmentation is ON, IP Identification(ID) field of the IP header is used, during packet reassembly on the destination host, to identify fragments which belong to the same packet. IP ID field is required to be unique and same across all fragments of an IP packet. IP packet fragments are identified by a tuple with following fields

(source address|destination address|protocol|IP-ID)

The Linux kernel derived this IP ID field from partial kernel space address returned by nethashmix() function, which is then used with a hash function to compute the IP ID field.

A remote user could observe this IP ID field to deduce the kernel space address bits used to derive its value. Thus leaking the hash key and potentially defeating KASLR.

Upstream fix: ------------- -> https://git.kernel.org/linus/355b98553789b646ed97ad801a619ff898471b92

Issue introduced by: -------------------- -> https://git.kernel.org/linus/b6a7719aedd7e5c0f2df7641aa47386111682df4 -> https://git.kernel.org/linus/5a352dd0a3aac03b443c94828dfd7144261c8636

Red Hat

Affected Software

9 affected componentsFixes available
redhat/kernel-rt<0:3.10.0-1127.rt56.1093.el7
0:3.10.0-1127.rt56.1093.el7
redhat/kernel<0:3.10.0-1127.el7
0:3.10.0-1127.el7
redhat/kernel<0:3.10.0-1062.26.1.el7
0:3.10.0-1062.26.1.el7
redhat/kernel-rt<0:4.18.0-193.rt13.51.el8
0:4.18.0-193.rt13.51.el8
redhat/kernel<0:4.18.0-193.el8
0:4.18.0-193.el8
IBM Data Risk Manager<=2.0.6
Linux Linux kernel>=4.1<=4.20.9
Linux Linux kernel>=5.0<5.0.8
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-1

Event History

Jul 5, 2019
CVE Published
via MITRE·10:07 PM
Data Sourced
via MITRE·10:07 PM
Description
Jul 15, 2019
Data Sourced
via Red Hat·11:16 AM
DescriptionSeverityAffected Software
Jan 11, 2024
Data Sourced
via Launchpad·11:12 PM
Description
Apr 28, 2025
Data Sourced
via Ubuntu·04:05 AM
RemedyDescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2019-10639?

CVE-2019-10639 has been classified with a moderate severity.

2

How do I fix CVE-2019-10639?

To fix CVE-2019-10639, update to the appropriate kernel version as specified in the remediation instructions.

3

Which systems are affected by CVE-2019-10639?

CVE-2019-10639 affects various Linux kernel versions, specifically those prior to 4.20.9 and certain Red Hat kernel versions.

4

Is there a specific patch for CVE-2019-10639?

Yes, kernel patches have been issued for CVE-2019-10639 in various distributions, including Red Hat and Debian.

5

Can remote users exploit CVE-2019-10639?

Yes, CVE-2019-10639 allows remote users to potentially exploit the vulnerability to leak hash keys used in the kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203