In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Treat NX as a valid SPTE bit for NPT Treat the NX bit as valid when using NPT, as KVM will set the NX bit when the NX huge page mitigation is enabled (mindblowing) and trigger the WARN that fires on reserved SPTE bits being set. KVM has required NX support for SVM since commit b26a71a1a5b9 ("KVM: SVM: Refuse to load kvm_amd if NX support is not available") for exactly this reason, but apparently it never occurred to anyone to actually test NPT with the mitigation enabled. ------------[ cut here ]------------ spte = 0x800000018a600ee7, level = 2, rsvd bits = 0x800f0000001fe000 WARNING: CPU: 152 PID: 15966 at arch/x86/kvm/mmu/spte.c:215 make_spte+0x327/0x340 [kvm] Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 10.48.0 01/27/2022 RIP: 0010:make_spte+0x327/0x340 [kvm] Call Trace: <TASK> tdp_mmu_map_handle_target_level+0xc3/0x230 [kvm] kvm_tdp_mmu_map+0x343/0x3b0 [kvm] direct_page_fault+0x1ae/0x2a0 [kvm] kvm_tdp_page_fault+0x7d/0x90 [kvm] kvm_mmu_page_fault+0xfb/0x2e0 [kvm] npf_interception+0x55/0x90 [kvm_amd] svm_invoke_exit_handler+0x31/0xf0 [kvm_amd] svm_handle_exit+0xf6/0x1d0 [kvm_amd] vcpu_enter_guest+0xb6d/0xee0 [kvm] ? kvm_pmu_trigger_event+0x6d/0x230 [kvm] vcpu_run+0x65/0x2c0 [kvm] kvm_arch_vcpu_ioctl_run+0x355/0x610 [kvm] kvm_vcpu_ioctl+0x551/0x610 [kvm] __se_sys_ioctl+0x77/0xc0 __x64_sys_ioctl+0x1d/0x20 do_syscall_64+0x44/0xa0 entry_SYSCALL_64_after_hwframe+0x46/0xb0 </TASK> ---[ end trace 0000000000000000 ]---

The version of kernel installed on the remote host is prior to 5.10.240-238.959. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2025-101 advisory.

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

    net: tap: NULL pointer derefence in dev_parse_header_protocol when skb->dev is null (CVE-2022-50073)

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

    KVM: x86/mmu: Treat NX as a valid SPTE bit for NPT (CVE-2022-50224)

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

    ACPI: PAD: fix crash in exit_round_robin() (CVE-2024-49935)

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

    codel: remove sch->q.qlen check before qdisc_tree_reduce_backlog() (CVE-2025-37798)

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

    sch_htb: make htb_qlen_notify() idempotent (CVE-2025-37932)

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

    serial: mctrl_gpio: split disable_ms into sync and no_sync APIs (CVE-2025-38040)

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

    virtio: break and reset virtio devices on device_shutdown() (CVE-2025-38064)

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

    rseq: Fix segfault on registration when rseq_cs is non-zero (CVE-2025-38067)

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

    VMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify (CVE-2025-38102)

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

    sch_hfsc: make hfsc_qlen_notify() idempotent (CVE-2025-38177)

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

    net_sched: sch_sfq: reject invalid perturb period (CVE-2025-38193)

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

    RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction (CVE-2025-38211)

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

    bcache: fix NULL pointer in cache_set_flush() (CVE-2025-38263)

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

    net/sched: Always pass notifications when child class becomes empty (CVE-2025-38350)

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

    drm/i915/gt: Fix timeline left held on VMA alloc error (CVE-2025-38389)

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

    NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN (CVE-2025-38393)

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

    nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails. (CVE-2025-38400)

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

    vsock/vmci: Clear the vmci transport packet properly when initializing it (CVE-2025-38403)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues 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.

  - KVM: x86/mmu: Treat NX as a valid SPTE bit for NPT Treat the NX bit as valid when using NPT, as KVM will     set the NX bit when the NX huge page mitigation is enabled (mindblowing) and trigger the WARN that fires     on reserved SPTE bits being set. KVM has required NX support for SVM since commit b26a71a1a5b9 (KVM: SVM:
    Refuse to load kvm_amd if NX support is not available) for exactly this reason, but apparently it never     occurred to anyone to actually test NPT with the mitigation enabled. ------------[ cut here ]------------     spte = 0x800000018a600ee7, level = 2, rsvd bits = 0x800f0000001fe000 WARNING: CPU: 152 PID: 15966 at     arch/x86/kvm/mmu/spte.c:215 make_spte+0x327/0x340 [kvm] Hardware name: Google, Inc.
    Arcadia_IT_80/Arcadia_IT_80, BIOS 10.48.0 01/27/2022 RIP: 0010:make_spte+0x327/0x340 [kvm] Call Trace:
    <TASK> tdp_mmu_map_handle_target_level+0xc3/0x230 [kvm] kvm_tdp_mmu_map+0x343/0x3b0 [kvm]     direct_page_fault+0x1ae/0x2a0 [kvm] kvm_tdp_page_fault+0x7d/0x90 [kvm] kvm_mmu_page_fault+0xfb/0x2e0 [kvm]     npf_interception+0x55/0x90 [kvm_amd] svm_invoke_exit_handler+0x31/0xf0 [kvm_amd]     svm_handle_exit+0xf6/0x1d0 [kvm_amd] vcpu_enter_guest+0xb6d/0xee0 [kvm] ? kvm_pmu_trigger_event+0x6d/0x230     [kvm] vcpu_run+0x65/0x2c0 [kvm] kvm_arch_vcpu_ioctl_run+0x355/0x610 [kvm] kvm_vcpu_ioctl+0x551/0x610 [kvm]
    __se_sys_ioctl+0x77/0xc0 __x64_sys_ioctl+0x1d/0x20 do_syscall_64+0x44/0xa0     entry_SYSCALL_64_after_hwframe+0x46/0xb0 </TASK> ---[ end trace 0000000000000000 ]--- (CVE-2022-50224)

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

ID	Name	Product	Family	Severity
246925	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2025-101 (ALASKERNEL-5.10-2025-101)	Nessus	Amazon Linux Local Security Checks	medium
243859	Linux Distros Unpatched Vulnerability : CVE-2022-50224	Nessus	Misc.	high

Detections

Analytics

CVE-2022-50224

medium

Tenable Plugins

medium

high