From abab191d33bc1cd36c5f94b14ef7062ac811dc94 Mon Sep 17 00:00:00 2001 From: amitU Date: Wed, 17 Sep 2025 13:40:44 -0400 Subject: [PATCH 1/2] Kernel CVES Analysis Sept17 2025 CVE-2025-39797 CVE-2025-39798 CVE-2025-39799 --- vulns/CVE-2025-39797.yml | 8 ++++++++ vulns/CVE-2025-39798.yml | 8 ++++++++ vulns/CVE-2025-39799.yml | 8 ++++++++ 3 files changed, 24 insertions(+) create mode 100644 vulns/CVE-2025-39797.yml create mode 100644 vulns/CVE-2025-39798.yml create mode 100644 vulns/CVE-2025-39799.yml diff --git a/vulns/CVE-2025-39797.yml b/vulns/CVE-2025-39797.yml new file mode 100644 index 0000000..b639dcc --- /dev/null +++ b/vulns/CVE-2025-39797.yml @@ -0,0 +1,8 @@ +reachability: Local +memory_corruption: No +bug_class: dropped packets +impact: Availability and Data Integrity issue +privileges_required: low +notes: Dropped packets can cause availability issue. Also, worth noting that packets being dropped can interfere with data so Integrity is also impacted. CONFIG_XFRM needs to be enabled for exploitation +author: Microsoft +version: 0.1 \ No newline at end of file diff --git a/vulns/CVE-2025-39798.yml b/vulns/CVE-2025-39798.yml new file mode 100644 index 0000000..46212e9 --- /dev/null +++ b/vulns/CVE-2025-39798.yml @@ -0,0 +1,8 @@ +reachability: Local +memory_corruption: No +bug_class: CWE-264: Permissions, Privileges, and Access Controls (Incorrect capabilities assignment after new mounting) +impact: Potential unauthorized access +privileges_required: low +notes: This is likely a bug not a security vulnerability. However, argument can be made that if capabilities are not set correctly, this could lead to unauthorized access (long shot possibility). CONFIG_NFS_FS or CONFIG_NFS_V4 or CONFIG_NFS_V3 need to be enabled for exploitation ; +author: Microsoft +version: 0.1 \ No newline at end of file diff --git a/vulns/CVE-2025-39799.yml b/vulns/CVE-2025-39799.yml new file mode 100644 index 0000000..8a85c4e --- /dev/null +++ b/vulns/CVE-2025-39799.yml @@ -0,0 +1,8 @@ +reachability: Local +memory_corruption: No +bug_class: Incorrect Control Flow Implementation +impact: Potential crash +privileges_required: low +notes: This will likely cause kernel warning. Possibility of kernel panic or crash is remote (and less probable) and would happen by flooding the logs with warning messages. +author: Microsoft +version: 0.1 \ No newline at end of file From 9f4c7bbdb80964a83f9ea337a0593edc4efa33eb Mon Sep 17 00:00:00 2001 From: amitU Date: Thu, 2 Oct 2025 10:22:29 -0400 Subject: [PATCH 2/2] addressed comments from dmell |CVE-2025-39838,CVE-2025-39857,CVE-2025-39862 --- vulns/CVE-2025-39797.yml | 4 ++-- vulns/CVE-2025-39798.yml | 8 ++++---- vulns/CVE-2025-39799.yml | 6 +++--- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/vulns/CVE-2025-39797.yml b/vulns/CVE-2025-39797.yml index b639dcc..f7fb837 100644 --- a/vulns/CVE-2025-39797.yml +++ b/vulns/CVE-2025-39797.yml @@ -1,8 +1,8 @@ reachability: Local -memory_corruption: No +memory_corruption: no bug_class: dropped packets impact: Availability and Data Integrity issue -privileges_required: low +privileges_required: yes notes: Dropped packets can cause availability issue. Also, worth noting that packets being dropped can interfere with data so Integrity is also impacted. CONFIG_XFRM needs to be enabled for exploitation author: Microsoft version: 0.1 \ No newline at end of file diff --git a/vulns/CVE-2025-39798.yml b/vulns/CVE-2025-39798.yml index 46212e9..0bfdf98 100644 --- a/vulns/CVE-2025-39798.yml +++ b/vulns/CVE-2025-39798.yml @@ -1,8 +1,8 @@ reachability: Local -memory_corruption: No -bug_class: CWE-264: Permissions, Privileges, and Access Controls (Incorrect capabilities assignment after new mounting) +memory_corruption: no +bug_class: Permissions, Privileges, and Access Controls (Incorrect capabilities assignment after new mounting) impact: Potential unauthorized access -privileges_required: low -notes: This is likely a bug not a security vulnerability. However, argument can be made that if capabilities are not set correctly, this could lead to unauthorized access (long shot possibility). CONFIG_NFS_FS or CONFIG_NFS_V4 or CONFIG_NFS_V3 need to be enabled for exploitation ; +privileges_required: yes +notes: This is likely a bug not a security vulnerability. However, argument can be made that if capabilities are not set correctly, this could lead to unauthorized access (long shot possibility). CONFIG_NFS_FS or CONFIG_NFS_V4 or CONFIG_NFS_V3 need to be enabled for exploitation author: Microsoft version: 0.1 \ No newline at end of file diff --git a/vulns/CVE-2025-39799.yml b/vulns/CVE-2025-39799.yml index 8a85c4e..e46b533 100644 --- a/vulns/CVE-2025-39799.yml +++ b/vulns/CVE-2025-39799.yml @@ -1,8 +1,8 @@ reachability: Local -memory_corruption: No +memory_corruption: no bug_class: Incorrect Control Flow Implementation impact: Potential crash -privileges_required: low -notes: This will likely cause kernel warning. Possibility of kernel panic or crash is remote (and less probable) and would happen by flooding the logs with warning messages. +privileges_required: yes +notes: This will likely cause kernel warning. Possibility of kernel panic or crash is remote (and less probable) and would happen by flooding the logs with warning messages author: Microsoft version: 0.1 \ No newline at end of file