kernel: NULL pointer dereference if close and fchownat system calls share a socket file descriptor
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 7 | |||
| kernel-alt-0:4.14.0-115.el7a | cpe:/o:redhat:enterprise_linux:7 | RHSA-2018:2948 | 2018-10-30T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2018-4210 | In net/socket.c in the Linux kernel through 4.17.1, there is a race condition between fchownat and close in cases where they target the same socket file descriptor, related to the sock_close and sockfs_setattr functions. fchownat does not increment the file descriptor reference count, which allows close to set the socket to NULL during fchownat's execution, leading to a NULL pointer dereference and system crash. |
Ubuntu USN |
USN-3752-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-3752-2 | Linux kernel (HWE) vulnerabilities |
Ubuntu USN |
USN-3752-3 | Linux kernel (Azure, GCP, OEM) vulnerabilities |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 6.3% (6.296% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.