In the Linux kernel, the following vulnerability has been resolved: hugetlbfs: don't delete error page from pagecache This change is very similar to the change that was made for shmem [1], and it solves the same problem but for HugeTLBFS instead. Currently, when poison is found in a HugeTLB page, the page is removed from the page cache. That means that attempting to map or read that hugepage in the future will result in a new hugepage being allocated instead of notifying the user that the page was poisoned. As [1] states, this is effectively memory corruption. The fix is to leave the page in the page cache. If the user attempts to use a poisoned HugeTLB page with a syscall, the syscall will fail with EIO, the same error code that shmem uses. For attempts to map the page, the thread will get a BUS_MCEERR_AR SIGBUS. [1]: commit a76054266661 ("mm: shmem: don't truncate page if memory failure happens")

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-013834 advisory.

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

    hugetlbfs: don't delete error page from pagecache

    This change is very similar to the change that was made for shmem [1], and     it solves the same problem but for HugeTLBFS instead.

    Currently, when poison is found in a HugeTLB page, the page is removed     from the page cache.  That means that attempting to map or read that     hugepage in the future will result in a new hugepage being allocated     instead of notifying the user that the page was poisoned.  As [1] states,     this is effectively memory corruption.

    The fix is to leave the page in the page cache.  If the user attempts to     use a poisoned HugeTLB page with a syscall, the syscall will fail with     EIO, the same error code that shmem uses.  For attempts to map the page,     the thread will get a BUS_MCEERR_AR SIGBUS.

    [1]: commit a76054266661 (mm: shmem: don't truncate page if memory failure happens)

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-011186 advisory.

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

    hugetlbfs: don't delete error page from pagecache

    This change is very similar to the change that was made for shmem [1], and     it solves the same problem but for HugeTLBFS instead.

    Currently, when poison is found in a HugeTLB page, the page is removed     from the page cache.  That means that attempting to map or read that     hugepage in the future will result in a new hugepage being allocated     instead of notifying the user that the page was poisoned.  As [1] states,     this is effectively memory corruption.

    The fix is to leave the page in the page cache.  If the user attempts to     use a poisoned HugeTLB page with a syscall, the syscall will fail with     EIO, the same error code that shmem uses.  For attempts to map the page,     the thread will get a BUS_MCEERR_AR SIGBUS.

    [1]: commit a76054266661 (mm: shmem: don't truncate page if memory failure happens)

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-013313 advisory.

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

    hugetlbfs: don't delete error page from pagecache

    This change is very similar to the change that was made for shmem [1], and     it solves the same problem but for HugeTLBFS instead.

    Currently, when poison is found in a HugeTLB page, the page is removed     from the page cache.  That means that attempting to map or read that     hugepage in the future will result in a new hugepage being allocated     instead of notifying the user that the page was poisoned.  As [1] states,     this is effectively memory corruption.

    The fix is to leave the page in the page cache.  If the user attempts to     use a poisoned HugeTLB page with a syscall, the syscall will fail with     EIO, the same error code that shmem uses.  For attempts to map the page,     the thread will get a BUS_MCEERR_AR SIGBUS.

    [1]: commit a76054266661 (mm: shmem: don't truncate page if memory failure happens)

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - hugetlbfs: don't delete error page from pagecache This change is very similar to the change that was made     for shmem [1], and it solves the same problem but for HugeTLBFS instead. Currently, when poison is found     in a HugeTLB page, the page is removed from the page cache. That means that attempting to map or read that     hugepage in the future will result in a new hugepage being allocated instead of notifying the user that     the page was poisoned. As [1] states, this is effectively memory corruption. The fix is to leave the page     in the page cache. If the user attempts to use a poisoned HugeTLB page with a syscall, the syscall will     fail with EIO, the same error code that shmem uses. For attempts to map the page, the thread will get a     BUS_MCEERR_AR SIGBUS. [1]: commit a76054266661 (mm: shmem: don't truncate page if memory failure     happens) (CVE-2022-49828)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Severity
309303	Unity Linux 20.1070a Security Update: kernel (UTSA-2026-013834)	Nessus	Unity Linux Local Security Checks	medium
308436	Unity Linux 20.1070e Security Update: kernel (UTSA-2026-011186)	Nessus	Unity Linux Local Security Checks	medium
308102	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-013313)	Nessus	Unity Linux Local Security Checks	medium
302981	EulerOS Virtualization 2.13.1 : kernel (EulerOS-SA-2026-1637)	Nessus	Huawei Local Security Checks	high
302971	EulerOS Virtualization 2.13.0 : kernel (EulerOS-SA-2026-1629)	Nessus	Huawei Local Security Checks	high
297598	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2026-1212)	Nessus	Huawei Local Security Checks	high
297592	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2026-1224)	Nessus	Huawei Local Security Checks	high
276115	TencentOS Server 4: kernel (TSSA-2025:0438)	Nessus	Tencent Local Security Checks	critical
245248	Linux Distros Unpatched Vulnerability : CVE-2022-49828	Nessus	Misc.	medium
170458	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2023-012 (ALASKERNEL-5.15-2023-012)	Nessus	Amazon Linux Local Security Checks	high

Detections

Analytics

CVE-2022-49828

medium

Tenable Plugins

medium

medium

medium

high

high

high

high

critical

medium

high