Vulnerability in Kernel package: i2c: i801: Don't generate an interrupt on bus reset

Kernel Updated 02 Oct 2025

Summary

04/06/2021
N/A
No i
Unrated
Not published

GSD-2021-1000592: i2c: i801: Don't generate an interrupt on bus reset. Affects Kernel versions >= 636752bcb5177a301d0266270661581de8624828, < b523feb7e8e44652f92f3babb953a976e7ccbbef. 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 Your last release was probably never penetration tested 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 that provides the core functionality and interfaces between hardware and software. It includes various drivers and modules to support different hardware devices. One such driver is the i2c driver, which enables communication with I2C devices. The i801 driver is a specific implementation of the i2c driver for Intel platforms. It allows the system to communicate with I2C devices connected to the Intel SMBus controller. However, a vulnerability has been discovered in the i801 driver that can lead to potential security issues.

Vulnerability Detail

The vulnerability in the i2c i801 driver occurs when an interrupt is generated on a bus reset. This can be exploited by an attacker to disrupt the normal operation of the system or potentially gain unauthorized access. The vulnerability was introduced in version v3.6 of the Linux Kernel and has been fixed in version v5.10.42. The impact and attack plausibility of this vulnerability have not been proven yet.

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 specific workaround mentioned for this vulnerability.

Conclusion

The vulnerability in the i2c i801 driver can pose security risks to Linux systems. It is crucial to update the Linux Kernel to the latest version to mitigate this vulnerability. For further support and assistance in vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The i2c i801 driver is a specific implementation of the i2c driver for Intel platforms. It allows the system to communicate with I2C devices connected to the Intel SMBus controller.

A bus reset is a process in which all devices on an I2C bus are reset to a known state. It is typically initiated by the master device to resolve any communication issues or conflicts.

The vulnerability can lead to disruption of the normal operation of the system and potentially unauthorized access by an attacker.

You can use tools like Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert Playground allows you to analyze your application's manifest file, such as package-lock.json, and provides real-time alerts for open-source vulnerabilities.

There is currently no known exploit for this vulnerability. However, it is still important to apply the recommended fix to ensure the security of your system.

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