Most recent entries from all

bdu:2026-03176

2026-10-03T20:41:38.494094+00:00

bdu:2026-03176

BELL-CVE-2025-71135

2026-10-03T20:41:38.494162+00:00

Affected: Alpaquita:stream: linux-lts

certfr-2026-avi-0166 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…

2026-10-03T20:41:38.494195+00:00

certfr-2026-avi-0166

EUVD-2026-320922

2026-10-03T20:41:38.494213+00:00

EUVD-2026-320922

fkie_cve-2025-71135

2026-10-03T20:41:38.494224+00:00

In the Linux kernel, the following vulnerability has been resolved:

md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt()

The variable mddev->private is first assigned to conf and then checked:

conf = mddev->private; if (!conf) ...

If conf is NULL, then mddev->private is also NULL. In this case, null-pointer dereferences can occur when calling raid5_quiesce():

raid5_quiesce(mddev, true); raid5_quiesce(mddev, false);

since mddev->private is assigned to conf again in raid5_quiesce(), and conf is dereferenced in several places, for example:

conf->quiesce = 0; wake_up(&conf->wait_for_quiescent);

To fix this issue, the function should unlock mddev and return before invoking raid5_quiesce() when conf is NULL, following the existing pattern in raid5_change_consistency_policy().

GHSA-w8wp-w464-6xr8

2026-10-03T20:41:38.494267+00:00

In the Linux kernel, the following vulnerability has been resolved:

md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt()

The variable mddev->private is first assigned to conf and then checked:

conf = mddev->private; if (!conf) ...

If conf is NULL, then mddev->private is also NULL. In this case, null-pointer dereferences can occur when calling raid5_quiesce():

raid5_quiesce(mddev, true); raid5_quiesce(mddev, false);

since mddev->private is assigned to conf again in raid5_quiesce(), and conf is dereferenced in several places, for example:

conf->quiesce = 0; wake_up(&conf->wait_for_quiescent);

To fix this issue, the function should unlock mddev and return before invoking raid5_quiesce() when conf is NULL, following the existing pattern in raid5_change_consistency_policy().

openSUSE-SU-2026:20287-1 — Security update for the Linux Kernel

2026-10-03T20:41:38.494292+00:00

Security update for the Linux Kernel

SUSE-SU-2026:0587-1 — Security update for the Linux Kernel

2026-10-03T20:41:38.494420+00:00

Security update for the Linux Kernel

UBUNTU-CVE-2025-71135

2026-10-03T20:41:38.494526+00:00

Affected: Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 140 more

In the Linux kernel, the following vulnerability has been resolved: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() The variable mddev->private is first assigned to conf and then checked: conf = mddev->private; if (!conf) ... If conf is NULL, then mddev->private is also NULL. In this case, null-pointer dereferences can occur when calling raid5_quiesce(): raid5_quiesce(mddev, true); raid5_quiesce(mddev, false); since mddev->private is assigned to conf again in raid5_quiesce(), and conf is dereferenced in several places, for example: conf->quiesce = 0; wake_up(&conf->wait_for_quiescent); To fix this issue, the function should unlock mddev and return before invoking raid5_quiesce() when conf is NULL, following the existing pattern in raid5_change_consistency_policy().

WID-SEC-W-2026-0119 — Linux Kernel: Mehrere Schwachstellen

2026-10-03T20:41:38.494698+00:00

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.