SUSE: Security Advisory (SUSE-SU-2021:2438-1)

Published: 2021-07-22 02:21:52
CVE Author: NIST National Vulnerability Database

CVSS Base Vector:



severity_date=2021-07-16 17:15:00 +0000 (Fri, 16 Jul 2021)

The remote host is missing an update for the 'Linux Kernel' Linux Distribution Package(s) announced via the SUSE-SU-2021:2438-1 advisory.

Detection Method:
Checks if a vulnerable Linux Distribution Package version is present on the target host.

Technical Details:
The SUSE Linux Enterprise 15 SP2 kernel was updated to receive various security and bugfixes. The following security bugs were fixed: CVE-2021-22555: A heap out-of-bounds write was discovered in net/netfilter/x_tables.c (bnc#1188116). CVE-2021-33909: Extremely large seq buffer allocations in seq_file could lead to buffer underruns and code execution (bsc#1188062). CVE-2021-3609: A use-after-free in can/bcm could have led to privilege escalation (bsc#1187215). CVE-2021-3612: An out-of-bounds memory write flaw was found in the joystick devices subsystem in the way the user calls ioctl JSIOCSBTNMAP. This flaw allowed a local user to crash the system or possibly escalate their privileges on the system. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability (bnc#1187585 ). CVE-2021-35039: kernel/module.c mishandled Signature Verification, aka CID-0c18f29aae7c. Without CONFIG_MODULE_SIG, verification that a kernel module is signed, for loading via init_module, did not occur for a module.sig_enforce=1 command-line argument (bnc#1188080). NOTE that SUSE kernels are configured with CONFIG_MODULE_SIG=y, so are not affected. The following non-security bugs were fixed: ACPI: APEI: fix synchronous external aborts in user-mode (git-fixes). ACPI: bus: Call kobject_put() in acpi_init() error path (git-fixes). ACPICA: Fix memory leak caused by _CID repair function (git-fixes). ACPI: EC: Make more Asus laptops use ECDT _GPE (git-fixes). ACPI: processor idle: Fix up C-state latency if not ordered (git-fixes). ACPI: property: Constify stubs for CONFIG_ACPI=n case (git-fixes). ACPI: resources: Add checks for ACPI IRQ override (git-fixes). ACPI: sysfs: Fix a buffer overrun problem with description_show() (git-fixes). ALSA: hda/realtek: Add another ALC236 variant support (git-fixes). ALSA: hda/realtek: Fix bass speaker DAC mapping for Asus UM431D (git-fixes). ALSA: intel8x0: Fix breakage at ac97 clock measurement (git-fixes). ALSA: isa: Fix error return code in snd_cmi8330_probe() (git-fixes). ALSA: usb-audio: fix rate on Ozone Z90 USB headset (git-fixes). ALSA: usb-audio: scarlett2: Fix wrong resume call (git-fixes). ALSA: usb-audio: scarlett2: Read mixer volumes at init time (git-fixes). ALSA: usb-audio: scarlett2: Read mux at init time (git-fixes). amdgpu: fix GEM obj leak in amdgpu_display_user_framebuffer_create (bsc#1152472) ASoC: atmel-i2s: Fix usage of capture and playback at the same time (git-fixes). ASoC: cs42l42: Correct definition of CS42L42_ADC_PDN_MASK (git-fixes). ASoC: hisilicon: fix missing clk_disable_unprepare() on error in hi6210_i2s_startup() (git-fixes). ASoC: mediatek: mtk-btcvsd: Fix an error handling path in 'mtk_btcvsd_snd_probe()' (git-fixes). ASoC: rsnd: tidyup loop on rsnd_adg_clk_query() (git-fixes). ata: ahci_sunxi: Disable DIPM (git-fixes). ath10k: add missing ... [Please see the references for more information on the vulnerabilities]

Affected Versions:
'Linux Kernel' Linux Distribution Package(s) on SUSE MicroOS 5.0, SUSE Linux Enterprise Workstation Extension 15-SP2, SUSE Linux Enterprise Module for Live Patching 15-SP2, SUSE Linux Enterprise Module for Legacy Software 15-SP2, SUSE Linux Enterprise Module for Development Tools 15-SP2, SUSE Linux Enterprise Module for Basesystem 15-SP2, SUSE Linux Enterprise High Availability 15-SP2.

Please install the updated Linux Distribution Package(s).

Solution Type:
Vendor Patch

Detection Type:
Linux Distribution Package

NIST (National Institute of Standards and Technology) NVD (National Vulnerability Database)


CVSS Score
SuSE Local Security Checks

Free Vulnerability Scanning, Assessment and Management

Mageni's Platform is packed with all the features you need to scan, assess and manage vulnerabilities like this - it is free, open source, lightning fast, reliable and scalable.


Frequently Asked Questions

No, you can scan concurrently as many assets as you want. Please note that you must be aware of the hardware requeriments of the platform to ensure a good performance.

No, you can add as many assest as you want. It doesn't matters if you have millions of assets, we won't charge you for that.

No. The software is completely free. We have no intention to charge you to use the software, in fact - it completely goes against our beliefs and business model.

A vulnerability is defined in the ISO 27002 standard as “A weakness of an asset or group of assets that can be exploited by one or more threats” (International Organization for Standardization, 2005)

We generate revenue by providing support and other services for customers that require a subscription so they get guaranteed support and enterprise services. To use Mageni's Platform is completely free, with no limits at all.

Yes. Mageni understands that there are professionals and businesses that need commercial support so Mageni provides an active support subscription with everything needed to run Mageni's Platform reliably and securely. More than software, it's access to security experts, knowledge resources, security updates, and support tools you can't get anywhere else. The subscription includes:

  • Ongoing delivery
    • Patches
    • Bug fixes
    • Updates
    • Upgrades
  • Technical support
    • 24/7 availability
    • Unlimited Incidents
    • Specialty-based routing
    • Multi-Channel
  • Commitments
    • Software certifications
    • Software assurance
    • SLA

No, we don't store the information of your vulnerabilities in our servers.

Vulnerability management is the process in which vulnerabilities in IT are identified and the risks of these vulnerabilities are evaluated. This evaluation leads to correcting the vulnerabilities and removing the risk or a formal risk acceptance by the management of an organization. The term vulnerability management is often confused with vulnerability scanning. Despite the fact both are related, there is an important difference between the two. Vulnerability scanning consists of using a computer program to identify vulnerabilities in networks, computer infrastructure or applications. Vulnerability management is the process surrounding vulnerability scanning, also taking into account other aspects such as risk acceptance, remediation etc. Source: "Implementing a Vulnerability Management Process". SANS Institute.

I am ready to start scanning for vulnerabilities