FlawAtlas
Search the atlas
SUSE-SU-2017:2548-1 Not scored

Security update for the Linux Kernel

The SUSE Linux Enterprise 11 SP4 kernel was updated to receive the following security fixes: - CVE-2017-1000251: The native Bluetooth stack in the Linux Kernel was vulnerable to a stack overflow while processing L2CAP configuration responses, resulting in a potential remote code execution vulnerability. [bnc#1057389]

Exploit probability Not scored
Published September 21, 2017
Required by Not available
Last source change February 4, 2026

02 / AFFECTED SOFTWARE

Affected packages

SUSE:Linux Enterprise Server 11 SP4 kernel-bigmem
SUSE:Linux Enterprise Server 11 SP4 kernel-default
SUSE:Linux Enterprise Server 11 SP4 kernel-ec2
SUSE:Linux Enterprise Server 11 SP4 kernel-pae
SUSE:Linux Enterprise Server 11 SP4 kernel-ppc64
SUSE:Linux Enterprise Server 11 SP4 kernel-source
SUSE:Linux Enterprise Server 11 SP4 kernel-syms
SUSE:Linux Enterprise Server 11 SP4 kernel-trace
SUSE:Linux Enterprise Server 11 SP4 kernel-xen
SUSE:Linux Enterprise Server for SAP Applications 11 SP4 kernel-bigmem
SUSE:Linux Enterprise Server for SAP Applications 11 SP4 kernel-default
SUSE:Linux Enterprise Server for SAP Applications 11 SP4 kernel-ec2
SUSE:Linux Enterprise Server for SAP Applications 11 SP4 kernel-pae
SUSE:Linux Enterprise Server for SAP Applications 11 SP4 kernel-ppc64
SUSE:Linux Enterprise Server for SAP Applications 11 SP4 kernel-source
SUSE:Linux Enterprise Server for SAP Applications 11 SP4 kernel-syms
SUSE:Linux Enterprise Server for SAP Applications 11 SP4 kernel-trace
SUSE:Linux Enterprise Server for SAP Applications 11 SP4 kernel-xen
SUSE:Linux Enterprise Software Development Kit 11 SP4 kernel-docs

03 / CONNECTIONS

Connected vulnerabilities

04 / EVIDENCE

Source records

Open Source Vulnerabilities SUSE-SU-2017:2548-1

The SUSE Linux Enterprise 11 SP4 kernel was updated to receive the following security fixes: - CVE-2017-1000251: The native Bluetooth stack in the Linux Kernel was vulnerable to a stack overflow while processing L2CAP configuration responses, resulting in a potential remote code execution vulnerability. [bnc#1057389]

View original source

05 / REFERENCES

Further evidence