CVE-2017-14497: Buffer Overflow

Published Sep 15, 2017
·
Updated

A buffer overflow was discovered in tpacketrcv() function in the Linux kernel since v4.6-rc1 through v4.13. A number of socket-related syscalls can be made to set up a configuration when each packet received by a network interface can cause writing up to 10 bytes to a kernel memory outside of a kernel buffer. This can cause unspecified kernel data corruption effects, including damage of in-memory and on-disk XFS data.

References:

https://marc.info/?l=linux-kernel&m=150394500728906&w=2

https://marc.info/?t=150394517700001&r=1&w=2

http://seclists.org/oss-sec/2017/q3/476

A kernel patch:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=edbd58be15a957f6a760c4a514cd475217eb97fd

Other sources

The tpacketrcv function in net/packet/afpacket.c in the Linux kernel before 4.13 mishandles vnet headers, which might allow local users to cause a denial of service (buffer overflow, and disk and memory corruption) or possibly have unspecified other impact via crafted system calls.

Affected Software

6 affected componentsFixes available
debian/linux
4.19.249-24.19.289-25.10.197-15.10.205-26.1.66-16.1.69-16.5.13-16.6.9-1
Google Android
Linux Linux Kernel>=4.6<4.9.51
Linux Linux Kernel>=4.10<4.12.14
Debian Linux=8.0
Debian Linux=9.0

Event History

Sep 15, 2017
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
Sep 18, 2017
Data Sourced
09:34 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Who can exploit this issue?

A local user with low privileges can exploit it. The CVSS vector indicates local access is required, no user interaction is needed, and no prior administrative privileges are required.

2

What must an attacker do to trigger the vulnerability?

The attacker must use socket-related system calls to create a packet-socket configuration involving vnet headers. Packets received by a network interface can then cause writes of up to 10 bytes outside a kernel buffer.

3

What are the likely consequences of successful exploitation?

The reported effects include kernel memory corruption, denial of service, and corruption of in-memory or on-disk XFS data. The issue may also have other unspecified impacts.

4

Which kernel versions are affected, and is a fix available?

The issue is reported from Linux v4.6-rc1 through v4.13, with affected code described as Linux kernel versions before 4.13. A kernel patch is available.

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