CVE-2017-18595
published 2019-09-04CVE-2017-18595: An issue was discovered in the Linux kernel before 4.14.11. A double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c.
PriorityP336high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.35%
27.6th percentile
An issue was discovered in the Linux kernel before 4.14.11. A double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c.
Affected
13 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 4.14.12-1 (bookworm) | linux 4.14.12-1 (bookworm) |
| linux | linux_kernel | >= 0 < 4.14.12-1 | 4.14.12-1 |
| linux | linux_kernel | >= 0 < 4.14.12-1 | 4.14.12-1 |
| linux | linux_kernel | >= 0 < 4.14.12-1 | 4.14.12-1 |
| linux | linux_kernel | >= 0 < 4.14.12-1 | 4.14.12-1 |
| linux | linux_kernel | >= 3.10 < 3.16.55 | 3.16.55 |
| linux | linux_kernel | >= 3.17 < 3.18.91 | 3.18.91 |
| linux | linux_kernel | >= 3.19 < 4.1.50 | 4.1.50 |
| linux | linux_kernel | >= 4.10 < 4.14.11 | 4.14.11 |
| linux | linux_kernel | >= 4.2 < 4.4.109 | 4.4.109 |
| linux | linux_kernel | >= 4.5 < 4.9.74 | 4.9.74 |
| opensuse | leap | — | — |
| opensuse | leap | — | — |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvdv2.07.2HIGHAV:L/AC:L/Au:N/C:C/I:C/A:C
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c
vendor_redhat·2019-09-04·CVSS 7.8
CVE-2017-18595 [HIGH] CWE-416 kernel: double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c
kernel: double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c
An issue was discovered in the Linux kernel before 4.14.11. A double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c.
A flaw was found in the allocate_trace_buffer in kernel/trace/trace.c in the debug subsystem, when failure to allocate a dynamic percpu area, a resource cleanup is called. The pointer (buf->buffer) still holds the address and is not set to NULL, which can cause a use-after-free problem, leading to a dangling pointer issue.
Mitigation: Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update as soon as possible.
Package: kernel (Red Hat E
Debian
CVE-2017-18595: linux - An issue was discovered in the Linux kernel before 4.14.11. A double free may be...
vendor_debian·2017·CVSS 7.8
CVE-2017-18595 [HIGH] CVE-2017-18595: linux - An issue was discovered in the Linux kernel before 4.14.11. A double free may be...
An issue was discovered in the Linux kernel before 4.14.11. A double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c.
Scope: local
bookworm: resolved (fixed in 4.14.12-1)
bullseye: resolved (fixed in 4.14.12-1)
forky: resolved (fixed in 4.14.12-1)
sid: resolved (fixed in 4.14.12-1)
trixie: resolved (fixed in 4.14.12-1)
GHSA
GHSA-rqcm-ff8h-8mfx: An issue was discovered in the Linux kernel before 4
ghsa_unreviewed·2022-05-24
CVE-2017-18595 [HIGH] CWE-415 GHSA-rqcm-ff8h-8mfx: An issue was discovered in the Linux kernel before 4
An issue was discovered in the Linux kernel before 4.14.11. A double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c.
OSV
CVE-2017-18595: An issue was discovered in the Linux kernel before 4
osv·2019-09-04·CVSS 7.8
CVE-2017-18595 [HIGH] CVE-2017-18595: An issue was discovered in the Linux kernel before 4
An issue was discovered in the Linux kernel before 4.14.11. A double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2017-18595 kernel: double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c [fedora-all]
bugzilla·2019-10-07·CVSS 7.8
CVE-2017-18595 [HIGH] CVE-2017-18595 kernel: double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c [fedora-all]
CVE-2017-18595 kernel: double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message
Bugzilla
CVE-2017-18595 kernel: double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c
bugzilla·2019-10-04·CVSS 7.8
CVE-2017-18595 [HIGH] CVE-2017-18595 kernel: double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c
CVE-2017-18595 kernel: double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c
An issue was discovered in the Linux kernel before 4.14.11. A double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c.
Reference:
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.11
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4397f04575c44e1440ec2e49b6302785c95fd2f8
Discussion:
Created kernel tracking bugs for this issue:
Affects: fedora-all [bug 1759138]
---
This was fixed for fedora in the 4.14.11 stable update, and never impacted any of the still currently supported versions of Fedora.
---
Mitigation:
Mitigation for this issue is either not available or the currently availab
http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00036.htmlhttp://lists.opensuse.org/opensuse-security-announce/2019-10/msg00037.htmlhttps://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.11https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4397f04575c44e1440ec2e49b6302785c95fd2f8http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00036.htmlhttp://lists.opensuse.org/opensuse-security-announce/2019-10/msg00037.htmlhttps://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.11https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4397f04575c44e1440ec2e49b6302785c95fd2f8
2019-09-04
Published