Evidence used
- No CISA KEV confirmation is currently recorded.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 0.15% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2025
CVE-2025-68340High confidence
team: Move team device type change at the end of team_port_add
Linux · Linux
7.8HighCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productHigh technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:Medium, lowered one band.downgradedsince 16 Oct 2026
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Canonical Ubuntu Security: 20 affected package states with no published fix
Distribution package intelligence
24 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.12.63-1 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Debian bookwormbookworm · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.1.162-1 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Debian forkyforky · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.17.11-1 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Debian sidsid · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.17.11-1 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-aws | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-azure | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-azure-fde | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-azure-nvidia | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-gcp | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-gke | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-gkeop | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-ibm | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-lowlatency | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-nvidia | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-nvidia-lowlatency | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-nvidia-tegra | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-oem-6.11 | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-oracle | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-raspi | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-raspi-realtime | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-realtime | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-riscv | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-xilinx | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 23 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2025-68340 · CSAF 2.0 · revision 42 · interimSUSE Product Security TeamCVE-2025-68340
The vendor explicitly identifies these products as affected by this CVE.
- kernel-default as component of SLES-LTSS-TERADATA 15 SP2
- kernel-source as component of SLES-LTSS-TERADATA 15 SP2
- kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
- kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP6
- kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
- kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP6
- kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP6
- kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
- cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
- dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
- gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
- kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
- Summary
- In the Linux kernel, the following vulnerability has been resolved: team: Move team device type change at the end of team_port_add Attempting to add a port device that is already up will expectedly fail, but not before modifying the team device header_ops. In the case of the syzbot reproducer the gre0 device is already in state UP when it attempts to add it as a port device of team0, this fails but before that header_ops->create of team0 is changed from eth_header to ipgre_header in the call to team_dev_type_check_change. Later when we end up in ipgre_header() struct ip_tunnel* points to nonsense as the private data of the device still holds a struct team. Example sequence of iproute2 commands to reproduce the hang/BUG(): ip link add dev team0 type team ip link add dev gre0 type gre ip link set dev gre0 up ip link set dev gre0 master team0 ip link set dev team0 up ping -I team0 1.1.1.1 Move team_dev_type_check_change down where all other checks have passed as it changes the dev type with no way to restore it in case one of the checks that follow it fail. Also make sure to preserve the origial mtu assignment: - If port_dev is not the same type as dev, dev takes mtu from port_dev - If port_dev is the same type as dev, port_dev takes mtu from dev This is done by adding a conditional before the call to dev_set_mtu to prevent it from assigning port_dev->mtu = dev->mtu and instead letting team_dev_type_check_change assign dev->mtu = port_dev->mtu. The conditional is needed because the patch moves the call to team_dev_type_check_change past dev_set_mtu. Testing: - team device driver in-tree selftests - Add/remove various devices as slaves of team device - syzbot
- Remediation
- To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
In the Linux kernel, the following vulnerability has been resolved: team: Move team device type change at the end of team_port_add Attempting to add a port device that is already up will expectedly fail, but not before modifying the team device header_ops. In the case of the syzbot reproducer the gre0 device is already in state UP when it attempts to add it as a port device of team0, this fails but before that header_ops->create of team0 is changed from eth_header to ipgre_header in the call to team_dev_type_check_change. Later when we end up in ipgre_header() struct ip_tunnel* points to nonsense as the private data of the device still holds a struct team. Example sequence of iproute2 commands to reproduce the hang/BUG(): ip link add dev team0 type team ip link add dev gre0 type gre ip link set dev gre0 up ip link set dev gre0 master team0 ip link set dev team0 up ping -I team0 1.1.1.1 Move team_dev_type_check_change down where all other checks have passed as it changes the dev type with no way to restore it in case one of the checks that follow it fail. Also make sure to preserve the origial mtu assignment: - If port_dev is not the same type as dev, dev takes mtu from port_dev - If port_dev is the same type as dev, port_dev takes mtu from dev This is done by adding a conditional before the call to dev_set_mtu to prevent it from assigning port_dev->mtu = dev->mtu and instead letting team_dev_type_check_change assign dev->mtu = port_dev->mtu. The conditional is needed because the patch moves the call to team_dev_type_check_change past dev_set_mtu. Testing: - team device driver in-tree selftests - Add/remove various devices as slaves of team device - syzbot
What
In the Linux kernel, the following vulnerability has been resolved: team: Move team device type change at the end of team_port_add Attempting to add a port device that is already up will expectedly fail, but not before modifying the team device header_ops. In the case of the syzbot reproducer the gre0 device is already in state UP when it attempts to add it as a port device of team0, this fails but before that header_ops->create of team0 is changed from eth_header to ipgre_header in the call to team_dev_type_check_change. Later when we end up in ipgre_header() struct ip_tunnel* points to nonsense as the private data of the device still holds a struct team. Example sequence of iproute2 commands to reproduce the hang/BUG(): ip link add dev team0 type team ip link add dev gre0 type gre ip link set dev gre0 up ip link set dev gre0 master team0 ip link set dev team0 up ping -I team0 1.1.1.1 Move team_dev_type_check_change down where all other checks have passed as it changes the dev type with no way to restore it in case one of the checks that follow it fail. Also make sure to preserve the origial mtu assignment: - If port_dev is not the same type as dev, dev takes mtu from port_dev - If port_dev is the same type as dev, port_dev takes mtu from dev This is done by adding a conditional before the call to dev_set_mtu to prevent it from assigning port_dev->mtu = dev->mtu and instead letting team_dev_type_check_change assign dev->mtu = port_dev->mtu. The conditional is needed because the patch moves the call to team_dev_type_check_change past dev_set_mtu. Testing: - team device driver in-tree selftests - Add/remove various devices as slaves of team device - syzbot
Why
The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
In the Linux kernel, the following vulnerability has been resolved: team: Move team device type change at the end of team_port_add Attempting to add a port device that is already up will expectedly fail, but not before modifying the team device header_ops. In the case of the syzbot reproducer the gre0 device is already in state UP when it attempts to add it as a port device of team0, this fails but before that header_ops->create of team0 is changed from eth_header to ipgre_header in the call to team_dev_type_check_change. Later when we end up in ipgre_header() struct ip_tunnel* points to nonsense as the private data of the device still holds a struct team. Example sequence of iproute2 commands to reproduce the hang/BUG(): ip link add dev team0 type team ip link add dev gre0 type gre ip link set dev gre0 up ip link set dev gre0 master team0 ip link set dev team0 up ping -I team0 1.1.1.1 Move team_dev_type_check_change down where all other checks have passed as it changes the dev type with no way to restore it in case one of the checks that follow it fail. Also make sure to preserve the origial mtu assignment: - If port_dev is not the same type as dev, dev takes mtu from port_dev - If port_dev is the same type as dev, port_dev takes mtu from dev This is done by adding a conditional before the call to dev_set_mtu to prevent it from assigning port_dev->mtu = dev->mtu and instead letting team_dev_type_check_change assign dev->mtu = port_dev->mtu. The conditional is needed because the patch moves the call to team_dev_type_check_change past dev_set_mtu. Testing: - team device driver in-tree selftests - Add/remove various devices as slaves of team device - syzbot
Why
The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Local
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration. - CWE not yet assigned
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- kernel-default as component of SLES-LTSS-TERADATA 15 SP2
- kernel-source as component of SLES-LTSS-TERADATA 15 SP2
- kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
- kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP6
- kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
- kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP6
- kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP6
- kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
- cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
- dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
- gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
- kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
- kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP3
- ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
- kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP6
- kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP6
- kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2
- kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2
- kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
- kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2
- kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
- kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP2
- kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP2
- kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- and 394 more
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 23 Dec 2025 · Last source change 16 Oct 2026, 15:09 UTC · CWE not yet assigned
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2025-204799
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD modified after enrichment
Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.SUSE Product Security Team ↗
- Before
- kernel-default as component of SLES-LTSS-TERADATA 15 SP2; kernel-source as component of SLES-LTSS-TERADATA 15 SP2; kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP3; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP6; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP6; kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4; kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4; kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4; kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4; and 397 more
- After
- kernel-default as component of SLES-LTSS-TERADATA 15 SP2; kernel-source as component of SLES-LTSS-TERADATA 15 SP2; kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP3; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP6; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP6; kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4; kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4; kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4; kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4; and 394 more
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 1d76efe1577b4323609b1bcbfafa8b731eda071a < f82d1fb65549de241fe312fcb2bcb8e0ad7b424d; 1d76efe1577b4323609b1bcbfafa8b731eda071a < c8b15b0d2eec3b5c7f585e5a53dfc8d36c818283; 1d76efe1577b4323609b1bcbfafa8b731eda071a < a74ab1b532ecc5f9106621a8f75b4c3d04466b35; 1d76efe1577b4323609b1bcbfafa8b731eda071a < e26235840fd961e4ebe5568f11a2a078cf726663; 1d76efe1577b4323609b1bcbfafa8b731eda071a < 4040b5e8963982a00aa821300cb746efc9f2947e; 1d76efe1577b4323609b1bcbfafa8b731eda071a < e3eed4f038214494af62c7d2d64749e5108ce6ca; 1d76efe1577b4323609b1bcbfafa8b731eda071a < 0ae9cfc454ea5ead5f3ddbdfe2e70270d8e2c8ef; 3.7 · Fixed: < 3.7; 5.10.259 ≤ 5.10.*; 5.15.199 ≤ 5.15.*; 6.1.162 ≤ 6.1.*; 6.6.123 ≤ 6.6.*; 6.12.61 ≤ 6.12.*; 6.17.11 ≤ 6.17.*; 6.18 ≤ *
- After
- Linux: 1d76efe1577b4323609b1bcbfafa8b731eda071a < f82d1fb65549de241fe312fcb2bcb8e0ad7b424d, 1d76efe1577b4323609b1bcbfafa8b731eda071a < c8b15b0d2eec3b5c7f585e5a53dfc8d36c818283, 1d76efe1577b4323609b1bcbfafa8b731eda071a < a74ab1b532ecc5f9106621a8f75b4c3d04466b35, 1d76efe1577b4323609b1bcbfafa8b731eda071a < e26235840fd961e4ebe5568f11a2a078cf726663, 1d76efe1577b4323609b1bcbfafa8b731eda071a < 4040b5e8963982a00aa821300cb746efc9f2947e, 1d76efe1577b4323609b1bcbfafa8b731eda071a < e3eed4f038214494af62c7d2d64749e5108ce6ca, 1d76efe1577b4323609b1bcbfafa8b731eda071a < 0ae9cfc454ea5ead5f3ddbdfe2e70270d8e2c8ef, 3.7 · Fixed: Linux: < 3.7, 5.10.259 ≤ 5.10.*, 5.15.199 ≤ 5.15.*, 6.1.162 ≤ 6.1.*, 6.6.123 ≤ 6.6.*, 6.12.61 ≤ 6.12.*, 6.17.11 ≤ 6.17.*, 6.18 ≤ *
CVE published
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.