Vulnerability in Kernel package: s390/pci: fix zpci_zdev_put() on reserve

Kernel Updated 02 Oct 2025

Summary

14/11/2021
N/A
No i
Unrated
Not published

GSD-2021-1002118: s390/pci: fix zpci_zdev_put() on reserve. Affects Kernel versions >= 2a671f77ee49f3e78997b77fdee139467ff6a598, < 4e5d794a2743f5a1e13ee1066ce37711f2696044. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Kernel package is a critical component of the Linux operating system, responsible for managing the system's core functionality. It provides essential services and interfaces for hardware devices, memory management, process scheduling, and more. The s390/pci module within the Kernel package specifically handles PCI device management for IBM System z architectures. This vulnerability affects the zpci_zdev_put() function in the s390/pci module, which is used to release a reserved PCI device. The vulnerability allows an attacker to exploit a flaw in the function, potentially leading to unauthorized access, privilege escalation, or denial of service.

Vulnerability Detail

The vulnerability arises from a coding error in the zpci_zdev_put() function of the s390/pci module. When attempting to release a reserved PCI device, the function fails to properly handle certain conditions, allowing an attacker to trigger a use-after-free or double-free vulnerability. This could result in the execution of arbitrary code, system crashes, or other malicious activities. The vulnerability was introduced in version v5.14 of the Linux Kernel and has been fixed in version v5.14.15.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to apply the official fix by updating the Kernel package to the recommended version.

Conclusion

The vulnerability in the Kernel package's s390/pci module could allow an attacker to execute arbitrary code, gain unauthorized access, escalate privileges, or cause denial of service. It is recommended to update the Kernel package to version v5.14.15 or later to address this vulnerability. For further support or assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability could allow an attacker to execute arbitrary code, gain unauthorized access, escalate privileges, or cause denial of service.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will provide real-time alerts for open-source vulnerabilities, including this one.

No, only versions starting from v5.14 up to v5.14.14 are affected. The vulnerability has been fixed in version v5.14.15.

Yes, this vulnerability can be exploited remotely if the affected system is accessible over a network.

There is no evidence of active exploitation of this vulnerability at the time of this report. However, it is crucial to apply the fix promptly to mitigate any potential risks.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback