GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

OESA-2025-2852 (CVE-2025-22079)

Vulnerability from osv_openeuler – Published: 2025-12-19 11:09 – Updated: 2026-08-06 11:09 – Source website
VLAI
Summary
kernel security update
Details

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

ocfs2: validate l_tree_depth to avoid out-of-bounds access

The l_tree_depth field is 16-bit (__le16), but the actual maximum depth is limited to OCFS2_MAX_PATH_DEPTH.

Add a check to prevent out-of-bounds access if l_tree_depth has an invalid value, which may occur when reading from a corrupted mounted disk [1].(CVE-2025-22079)

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

mfd: ene-kb3930: Fix a potential NULL pointer dereference

The off_gpios could be NULL. Add missing check in the kb3930_probe(). This is similar to the issue fixed in commit b1ba8bcb2d1f ("backlight: hx8357: Fix potential NULL pointer dereference").

This was detected by our static analysis tool.(CVE-2025-23146)

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

jbd2: remove wrong sb->s_sequence check

Journal emptiness is not determined by sb->s_sequence == 0 but rather by sb->s_start == 0 (which is set a few lines above). Furthermore 0 is a valid transaction ID so the check can spuriously trigger. Remove the invalid WARN_ON.(CVE-2025-37839)

In the Linux kernel, bit_putcs_aligned()/unaligned() derived the glyph pointer from the character value masked by 0xff/0x1ff, which may exceed the actual font's glyph count and read past the end of the built-in font array. Clamp the index to the actual glyph count before computing the address. This fixes a global out-of-bounds read reported by syzbot.(CVE-2025-40322)


{
  "affected": [
    {
      "ecosystem_specific": {
        "aarch64": [
          "kernel-5.10.0-295.0.0.197.oe2203sp3.aarch64.rpm",
          "kernel-debuginfo-5.10.0-295.0.0.197.oe2203sp3.aarch64.rpm",
          "kernel-debugsource-5.10.0-295.0.0.197.oe2203sp3.aarch64.rpm",
          "kernel-devel-5.10.0-295.0.0.197.oe2203sp3.aarch64.rpm",
          "kernel-headers-5.10.0-295.0.0.197.oe2203sp3.aarch64.rpm",
          "kernel-source-5.10.0-295.0.0.197.oe2203sp3.aarch64.rpm",
          "kernel-tools-5.10.0-295.0.0.197.oe2203sp3.aarch64.rpm",
          "kernel-tools-debuginfo-5.10.0-295.0.0.197.oe2203sp3.aarch64.rpm",
          "kernel-tools-devel-5.10.0-295.0.0.197.oe2203sp3.aarch64.rpm",
          "perf-5.10.0-295.0.0.197.oe2203sp3.aarch64.rpm",
          "perf-debuginfo-5.10.0-295.0.0.197.oe2203sp3.aarch64.rpm",
          "python3-perf-5.10.0-295.0.0.197.oe2203sp3.aarch64.rpm",
          "python3-perf-debuginfo-5.10.0-295.0.0.197.oe2203sp3.aarch64.rpm"
        ],
        "src": [
          "kernel-5.10.0-295.0.0.197.oe2203sp3.src.rpm"
        ],
        "x86_64": [
          "kernel-5.10.0-295.0.0.197.oe2203sp3.x86_64.rpm",
          "kernel-debuginfo-5.10.0-295.0.0.197.oe2203sp3.x86_64.rpm",
          "kernel-debugsource-5.10.0-295.0.0.197.oe2203sp3.x86_64.rpm",
          "kernel-devel-5.10.0-295.0.0.197.oe2203sp3.x86_64.rpm",
          "kernel-headers-5.10.0-295.0.0.197.oe2203sp3.x86_64.rpm",
          "kernel-source-5.10.0-295.0.0.197.oe2203sp3.x86_64.rpm",
          "kernel-tools-5.10.0-295.0.0.197.oe2203sp3.x86_64.rpm",
          "kernel-tools-debuginfo-5.10.0-295.0.0.197.oe2203sp3.x86_64.rpm",
          "kernel-tools-devel-5.10.0-295.0.0.197.oe2203sp3.x86_64.rpm",
          "perf-5.10.0-295.0.0.197.oe2203sp3.x86_64.rpm",
          "perf-debuginfo-5.10.0-295.0.0.197.oe2203sp3.x86_64.rpm",
          "python3-perf-5.10.0-295.0.0.197.oe2203sp3.x86_64.rpm",
          "python3-perf-debuginfo-5.10.0-295.0.0.197.oe2203sp3.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:22.03-LTS-SP3",
        "name": "kernel",
        "purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-22.03-LTS-SP3"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.10.0-295.0.0.197.oe2203sp3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "severity": "High"
  },
  "details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: validate l_tree_depth to avoid out-of-bounds access\n\nThe l_tree_depth field is 16-bit (__le16), but the actual maximum depth is\nlimited to OCFS2_MAX_PATH_DEPTH.\n\nAdd a check to prevent out-of-bounds access if l_tree_depth has an invalid\nvalue, which may occur when reading from a corrupted mounted disk [1].(CVE-2025-22079)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmfd: ene-kb3930: Fix a potential NULL pointer dereference\n\nThe off_gpios could be NULL. Add missing check in the kb3930_probe().\nThis is similar to the issue fixed in commit b1ba8bcb2d1f\n(\u0026quot;backlight: hx8357: Fix potential NULL pointer dereference\u0026quot;).\n\nThis was detected by our static analysis tool.(CVE-2025-23146)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njbd2: remove wrong sb-\u0026gt;s_sequence check\n\nJournal emptiness is not determined by sb-\u0026gt;s_sequence == 0 but rather by\nsb-\u0026gt;s_start == 0 (which is set a few lines above). Furthermore 0 is a\nvalid transaction ID so the check can spuriously trigger. Remove the\ninvalid WARN_ON.(CVE-2025-37839)\n\nIn the Linux kernel, bit_putcs_aligned()/unaligned() derived the glyph pointer from the character value masked by 0xff/0x1ff, which may exceed the actual font\u0026apos;s glyph count and read past the end of the built-in font array. Clamp the index to the actual glyph count before computing the address. This fixes a global out-of-bounds read reported by syzbot.(CVE-2025-40322)",
  "id": "OESA-2025-2852",
  "modified": "2026-08-06T11:09:59Z",
  "published": "2025-12-19T11:09:59Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2852"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-22079"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-23146"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-37839"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-40322"
    }
  ],
  "schema_version": "1.7.2",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "kernel security update",
  "upstream": [
    "CVE-2025-22079",
    "CVE-2025-23146",
    "CVE-2025-37839",
    "CVE-2025-40322"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…