NVIDIA T241-FABRIC-4 Erratum Workaround in Linux Kernel

linux Updated 02 Oct 2025

Summary

18/09/2025
N/A
No i
Unrated
Not published

CVE-2023-53383: In the Linux kernel, the following vulnerability has been resolved: irqchip/gicv3: Workaround for NVIDIA erratum T241-FABRIC-4 The T241 platform suffers from the T241-FABRIC-4 erratum which causes unexpected behavior in... Affects linux versions 5.10.103-1 – 6.9.9-1. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The Linux kernel is the core component of the Linux operating system, responsible for managing system resources and facilitating communication between hardware and software. It is widely used across various platforms, including servers, desktops, and embedded systems. The kernel's functionality includes process management, memory management, device drivers, and system calls. The vulnerability in question affects NVIDIA server platforms utilizing the T241 chip, particularly when multiple chips are interconnected, leading to potential system instability.

Vulnerability Detail

In the Linux kernel, a vulnerability has been identified related to the NVIDIA T241 platform, specifically the T241-FABRIC-4 erratum. This issue arises when multiple transactions are received simultaneously from different sources, causing unexpected behavior in the ARM Generic Interrupt Controller (GIC). The erratum can lead to GIC state corruption, resulting in kernel panics and unpredictable system behavior. The problem is exacerbated in configurations with more than two sockets, where interleaving of transfer packets can occur, impacting the integrity of the system.

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

As a temporary workaround, implement a solution that directs read accesses to the GICD_In{E} registers to the chip that owns the SPI. Additionally, disable GICv4.x features to mitigate the impact of the erratum. The gic_configure_irq() function can be modified to use the same alias region for both read and write operations to GICD_ICFGR.

Conclusion

The vulnerability related to the NVIDIA T241-FABRIC-4 erratum in the Linux kernel poses significant risks to systems utilizing multiple T241 chips. It is crucial for users to update their systems to the patched versions or implement the recommended workarounds to ensure stability and security.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

It is a hardware issue affecting NVIDIA T241 platforms that can cause unexpected behavior in the GIC when multiple transactions are received simultaneously.

The vulnerability can lead to GIC state corruption, resulting in kernel panics and unpredictable behavior, particularly in systems with more than two T241 chips.

You should update your Linux kernel to the patched version available for your Debian distribution to resolve the vulnerability.

Yes, a workaround involves directing read accesses to the GICD_In{E} registers to the appropriate chip and disabling GICv4.x features.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just a manifest file like package-lock.json.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

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