Количество 15
Количество 15
CVE-2026-63952
In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEAL_WRITE When SEAL_EXEC is added, SEAL_WRITE is implied to make W^X. But the implied seal is set after the check that makes sure the memfd can not have any writable mappings. This means one can use SEAL_EXEC to apply SEAL_WRITE while having writeable mappings. This breaks the contract that SEAL_WRITE provides and can be used by an attacker to pass a memfd that appears to be write sealed but can still be modified arbitrarily. Fix this by adding the implied seals before the call for mapping_deny_writable() is done.
CVE-2026-63952
In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEAL_WRITE When SEAL_EXEC is added, SEAL_WRITE is implied to make W^X. But the implied seal is set after the check that makes sure the memfd can not have any writable mappings. This means one can use SEAL_EXEC to apply SEAL_WRITE while having writeable mappings. This breaks the contract that SEAL_WRITE provides and can be used by an attacker to pass a memfd that appears to be write sealed but can still be modified arbitrarily. Fix this by adding the implied seals before the call for mapping_deny_writable() is done.
CVE-2026-63952
In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEAL_WRITE When SEAL_EXEC is added, SEAL_WRITE is implied to make W^X. But the implied seal is set after the check that makes sure the memfd can not have any writable mappings. This means one can use SEAL_EXEC to apply SEAL_WRITE while having writeable mappings. This breaks the contract that SEAL_WRITE provides and can be used by an attacker to pass a memfd that appears to be write sealed but can still be modified arbitrarily. Fix this by adding the implied seals before the call for mapping_deny_writable() is done.
CVE-2026-63952
In the Linux kernel, the following vulnerability has been resolved: m ...
ROS-20261009-80-0186
Уязвимость kernel-lt
GHSA-6pc4-h32v-99rg
In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEAL_WRITE When SEAL_EXEC is added, SEAL_WRITE is implied to make W^X. But the implied seal is set after the check that makes sure the memfd can not have any writable mappings. This means one can use SEAL_EXEC to apply SEAL_WRITE while having writeable mappings. This breaks the contract that SEAL_WRITE provides and can be used by an attacker to pass a memfd that appears to be write sealed but can still be modified arbitrarily. Fix this by adding the implied seals before the call for mapping_deny_writable() is done.
RLSA-2026:57251
Important: kernel security, bug fix, and enhancement update
ELSA-2026-57251
ELSA-2026-57251: kernel security, bug fix, and enhancement update (IMPORTANT)
RLSA-2026:57252
Important: kernel security, bug fix, and enhancement update
ELSA-2026-57252
ELSA-2026-57252: kernel security, bug fix, and enhancement update (IMPORTANT)
SUSE-SU-2026:3602-1
Security update for the Linux Kernel
SUSE-SU-2026:3810-1
Security update for the Linux Kernel
SUSE-SU-2026:3790-1
Security update for the Linux Kernel
openSUSE-SU-2026:21555-1
Security update for the Linux Kernel
ELSA-2026-500248
ELSA-2026-500248: Unbreakable Enterprise kernel security update (IMPORTANT)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | CVE-2026-63952 In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEAL_WRITE When SEAL_EXEC is added, SEAL_WRITE is implied to make W^X. But the implied seal is set after the check that makes sure the memfd can not have any writable mappings. This means one can use SEAL_EXEC to apply SEAL_WRITE while having writeable mappings. This breaks the contract that SEAL_WRITE provides and can be used by an attacker to pass a memfd that appears to be write sealed but can still be modified arbitrarily. Fix this by adding the implied seals before the call for mapping_deny_writable() is done. | CVSS3: 8.4 | 0% Низкий | 3 месяца назад |
 | CVE-2026-63952 In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEAL_WRITE When SEAL_EXEC is added, SEAL_WRITE is implied to make W^X. But the implied seal is set after the check that makes sure the memfd can not have any writable mappings. This means one can use SEAL_EXEC to apply SEAL_WRITE while having writeable mappings. This breaks the contract that SEAL_WRITE provides and can be used by an attacker to pass a memfd that appears to be write sealed but can still be modified arbitrarily. Fix this by adding the implied seals before the call for mapping_deny_writable() is done. | CVSS3: 7 | 0% Низкий | 3 месяца назад |
 | CVE-2026-63952 In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEAL_WRITE When SEAL_EXEC is added, SEAL_WRITE is implied to make W^X. But the implied seal is set after the check that makes sure the memfd can not have any writable mappings. This means one can use SEAL_EXEC to apply SEAL_WRITE while having writeable mappings. This breaks the contract that SEAL_WRITE provides and can be used by an attacker to pass a memfd that appears to be write sealed but can still be modified arbitrarily. Fix this by adding the implied seals before the call for mapping_deny_writable() is done. | CVSS3: 8.4 | 0% Низкий | 3 месяца назад |
| CVE-2026-63952 In the Linux kernel, the following vulnerability has been resolved: m ... | CVSS3: 8.4 | 0% Низкий | 3 месяца назад |
 | ROS-20261009-80-0186 Уязвимость kernel-lt | CVSS3: 8.4 | 0% Низкий | 17 дней назад |
| GHSA-6pc4-h32v-99rg In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEAL_WRITE When SEAL_EXEC is added, SEAL_WRITE is implied to make W^X. But the implied seal is set after the check that makes sure the memfd can not have any writable mappings. This means one can use SEAL_EXEC to apply SEAL_WRITE while having writeable mappings. This breaks the contract that SEAL_WRITE provides and can be used by an attacker to pass a memfd that appears to be write sealed but can still be modified arbitrarily. Fix this by adding the implied seals before the call for mapping_deny_writable() is done. | CVSS3: 8.4 | 0% Низкий | 3 месяца назад |
 | RLSA-2026:57251 Important: kernel security, bug fix, and enhancement update | 2 месяца назад | ||
| ELSA-2026-57251 ELSA-2026-57251: kernel security, bug fix, and enhancement update (IMPORTANT) | 2 месяца назад | ||
| RLSA-2026:57252 Important: kernel security, bug fix, and enhancement update | 2 месяца назад | ||
| ELSA-2026-57252 ELSA-2026-57252: kernel security, bug fix, and enhancement update (IMPORTANT) | 2 месяца назад | ||
 | SUSE-SU-2026:3602-1 Security update for the Linux Kernel | 2 месяца назад | ||
| SUSE-SU-2026:3810-1 Security update for the Linux Kernel | 2 месяца назад | ||
| SUSE-SU-2026:3790-1 Security update for the Linux Kernel | 2 месяца назад | ||
| openSUSE-SU-2026:21555-1 Security update for the Linux Kernel | 2 месяца назад | ||
| ELSA-2026-500248 ELSA-2026-500248: Unbreakable Enterprise kernel security update (IMPORTANT) | около 2 месяцев назад |
Уязвимостей на страницу