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

Published: 2021-08-19 02:25:52
CVE Author: NIST National Vulnerability Database

CVSS Base Vector:



severity_date=2021-07-08 05:15:00 +0000 (Thu, 08 Jul 2021)

The remote host is missing an update for the 'Linux Kernel' Linux Distribution Package(s) announced via the SUSE-SU-2021:2756-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-3659: Fixed a NULL pointer dereference in llsec_key_alloc() in net/mac802154/llsec.c (bsc#1188876). CVE-2021-21781: Fixed a information disclosure vulnerability in the ARM SIGPAGE (bsc#1188445). CVE-2021-22543: Fixed improper handling of VM_IOVM_PFNMAP vmas in KVM, which could bypass RO checks and can lead to pages being freed while still accessible by the VMM and guest. This allowed users with the ability to start and control a VM to read/write random pages of memory and can result in local privilege escalation (bsc#1186482). CVE-2021-37576: Fixed an issue on the powerpc platform, where a KVM guest OS user could cause host OS memory corruption via rtas_args.nargs (bsc#1188838). The following non-security bugs were fixed: ACPI: AMBA: Fix resource name in /proc/iomem (git-fixes). ACPI: video: Add quirk for the Dell Vostro 3350 (git-fixes). ALSA: ac97: fix PM reference leak in ac97_bus_remove() (git-fixes). ALSA: bebob: add support for ToneWeal FW66 (git-fixes). ALSA: hda: Add IRQ check for platform_get_irq() (git-fixes). ALSA: hdmi: Expose all pins on MSI MS-7C94 board (git-fixes). ALSA: ppc: fix error return code in snd_pmac_probe() (git-fixes). ALSA: sb: Fix potential ABBA deadlock in CSP driver (git-fixes). ALSA: sb: Fix potential double-free of CSP mixer elements (git-fixes). ALSA: usb-audio: Add registration quirk for JBL Quantum headsets (git-fixes). ALSA: usb-audio: scarlett2: Fix 18i8 Gen 2 PCM Input count (git-fixes). ALSA: usb-audio: scarlett2: Fix 6i6 Gen 2 line out descriptions (git-fixes). ALSA: usb-audio: scarlett2: Fix data_mutex lock (git-fixes). ALSA: usb-audio: scarlett2: Fix scarlett2_*_ctl_put() return values (git-fixes). ALSA: usx2y: Do not call free_pages_exact() with NULL address (git-fixes). ARM: ensure the signal page contains defined contents (bsc#1188445). ASoC: Intel: kbl_da7219_max98357a: shrink platform_id below 20 characters (git-fixes). ASoC: img: Fix PM reference leak in img_i2s_in_probe() (git-fixes). ASoC: rt5631: Fix regcache sync errors on resume (git-fixes). ASoC: soc-core: Fix the error return code in snd_soc_of_parse_audio_routing() (git-fixes). ASoC: tegra: Set driver_name=tegra for all machine drivers (git-fixes). Bluetooth: Fix the HCI to MGMT status conversion table (git-fixes). Bluetooth: Shutdown controller after workqueues are flushed or cancelled (git-fixes). Bluetooth: btusb: Fixed too many in-token issue for Mediatek Chip (git-fixes). Bluetooth: btusb: fix bt fiwmare downloading failure issue for qca btsoc (git-fixes). Input: hideep - fix the uninitialized use in hideep_nvm_unlock() (git-fixes). Input: ili210x - add missing negation for touch indication on ili210x (git-fixes). KVM: LAPIC: Prevent setting the tscdeadline ... [Please see the references for more information on the vulnerabilities]

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

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