CVE-2024-35818

CVE-2024-35818 : In the Linux kernel, LoongArch-specific fix defines the __io_aw() hook as mmiowb() to address issues from removing explicit mmiowb() invocations in drivers. The patch relocates the mmiowb tracking to handle mutex-protected MMIO, since some MMIO regions (e.g., in radeon) are guard...

CVE-2024-35818 LoongArch: Define the __io_aw() hook as mmiowb()

In the Linux kernel, the following vulnerability has been resolved: LoongArch: Define the ioaw hook as mmiowb Commit fb24ea52f78e0d595852e "drivers: Remove explicit invocations of mmiowb" remove all mmiowb in drivers, but it says: "NOTE: mmiowb has only ever guaranteed ordering in conjunction wit...

CVE-2024-35818

In the Linux kernel, the following vulnerability has been resolved: LoongArch: Define the ioaw hook as mmiowb Commit fb24ea52f78e0d595852e "drivers: Remove explicit invocations of mmiowb" remove all mmiowb in drivers, but it says: "NOTE: mmiowb has only ever guaranteed ordering in conjunction wit...

CVE-2024-35818 LoongArch: Define the __io_aw() hook as mmiowb()

In the Linux kernel, the following vulnerability has been resolved: LoongArch: Define the ioaw hook as mmiowb Commit fb24ea52f78e0d595852e "drivers: Remove explicit invocations of mmiowb" remove all mmiowb in drivers, but it says: "NOTE: mmiowb has only ever guaranteed ordering in conjunction wit...

CVE-2024-35818 LoongArch: Define the __io_aw() hook as mmiowb()

In the Linux kernel, the following vulnerability has been resolved: LoongArch: Define the ioaw hook as mmiowb Commit fb24ea52f78e0d595852e "drivers: Remove explicit invocations of mmiowb" remove all mmiowb in drivers, but it says: "NOTE: mmiowb has only ever guaranteed ordering in conjunction wit...

SUSE CVE-2024-26841

In the Linux kernel, the following vulnerability has been resolved: LoongArch: Update cpusiblingmap when disabling nonboot CPUs Update cpusiblingmap when disabling nonboot CPUs by defining & calling clearcpusiblingmap, otherwise we get such errors on SMT systems: jump label: negative count!...

CVE-2024-26841

A flaw was found in the Linux kernel. This vulnerability specifically affects LoongArch processors. The issue is related to the CPU sibling map, which is not correctly updated when non-boot CPUs are disabled. This issue could lead to errors on Symmetric Multi-Threading SMT systems, such as...

CVE-2024-26841

In the Linux kernel, the following vulnerability has been resolved: LoongArch: Update cpusiblingmap when disabling nonboot CPUs Update cpusiblingmap when disabling nonboot CPUs by defining & calling clearcpusiblingmap, otherwise we get such errors on SMT systems: jump label: negative count!...

AZL-59453 CVE-2024-26841 affecting package kernel 5.15.200.1-1

In the Linux kernel, the following vulnerability has been resolved: LoongArch: Update cpusiblingmap when disabling nonboot CPUs Update cpusiblingmap when disabling nonboot CPUs by defining & calling clearcpusiblingmap, otherwise we get such errors on SMT systems: jump label: negative count!...

DEBIAN-CVE-2024-26841

In the Linux kernel, the following vulnerability has been resolved: LoongArch: Update cpusiblingmap when disabling nonboot CPUs Update cpusiblingmap when disabling nonboot CPUs by defining & calling clearcpusiblingmap, otherwise we get such errors on SMT systems: jump label: negative count!...

CVE-2024-26841

In the Linux kernel, the following vulnerability has been resolved: LoongArch: Update cpusiblingmap when disabling nonboot CPUs Update cpusiblingmap when disabling nonboot CPUs by defining & calling clearcpusiblingmap, otherwise we get such errors on SMT systems: jump label: negative count!...

UBUNTU-CVE-2024-26841

In the Linux kernel, the following vulnerability has been resolved: LoongArch: Update cpusiblingmap when disabling nonboot CPUs Update cpusiblingmap when disabling nonboot CPUs by defining & calling clearcpusiblingmap, otherwise we get such errors on SMT systems: jump label: negative count!...

CVE-2024-26841

In the Linux kernel, the following vulnerability has been resolved: LoongArch: Update cpusiblingmap when disabling nonboot CPUs Update cpusiblingmap when disabling nonboot CPUs by defining & calling clearcpusiblingmap, otherwise we get such errors on SMT systems: jump label: negative count!...

CVE-2024-26841 LoongArch: Update cpu_sibling_map when disabling nonboot CPUs

In the Linux kernel, the following vulnerability has been resolved: LoongArch: Update cpusiblingmap when disabling nonboot CPUs Update cpusiblingmap when disabling nonboot CPUs by defining & calling clearcpusiblingmap, otherwise we get such errors on SMT systems: jump label: negative count!...

CVE-2024-26841

Exposed CVE-2024-26841 affecting LoongArch Linux kernels: when disabling nonboot CPUs, cpu_sibling_map is not updated, risking negative jump-label counts on SMT systems. A fix defines and calls clear_cpu_sibling_map() to refresh the mapping, mitigating a potential kernel instability (jump_label w...

CVE-2024-26841 LoongArch: Update cpu_sibling_map when disabling nonboot CPUs

In the Linux kernel, the following vulnerability has been resolved: LoongArch: Update cpusiblingmap when disabling nonboot CPUs Update cpusiblingmap when disabling nonboot CPUs by defining & calling clearcpusiblingmap, otherwise we get such errors on SMT systems: jump label: negative count!...

CVE-2024-26841 LoongArch: Update cpu_sibling_map when disabling nonboot CPUs

In the Linux kernel, the following vulnerability has been resolved: LoongArch: Update cpusiblingmap when disabling nonboot CPUs Update cpusiblingmap when disabling nonboot CPUs by defining & calling clearcpusiblingmap, otherwise we get such errors on SMT systems: jump label: negative count!...

PT-2024-21526 · Linux +1 · Linux Kernel +1

Name of the Vulnerable Software and Affected Versions: Linux kernel versions prior to 6.8.0-rc5+ Description: The issue is related to the LoongArch architecture in the Linux kernel. When disabling non-boot CPUs, the cpu sibling map is not updated correctly, leading to errors on SMT systems, such ...

SUSE CVE-2024-26768

In the Linux kernel, the following vulnerability has been resolved: LoongArch: Change acpicorepicNRCPUS to acpicorepicMAXCOREPIC With default config, the value of NRCPUS is 64. When HW platform has more then 64 cpus, system will crash on these platforms. MAXCOREPIC is the maximum cpu number in MA...

CVE-2024-26768

In the Linux kernel, the following vulnerability has been resolved: LoongArch: Change acpicorepicNRCPUS to acpicorepicMAXCOREPIC With default config, the value of NRCPUS is 64. When HW platform has more then 64 cpus, system will crash on these platforms. MAXCOREPIC is the maximum cpu number in MA...