OESA-2025-1596 (CVE-2022-49787)

Vulnerability from osv_openeuler – Published: 2025-06-06 11:08 – Updated: 2026-08-06 11:08 – 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:

mmc: sdhci-pci: Fix possible memory leak caused by missing pci_dev_put()

pci_get_device() will increase the reference count for the returned pci_dev. We need to use pci_dev_put() to decrease the reference count before amd_probe() returns. There is no problem for the 'smbus_dev == NULL' branch because pci_dev_put() can also handle the NULL input parameter case.(CVE-2022-49787)

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

media: dw2102: Fix null-ptr-deref in dw2102_i2c_transfer()

In dw2102_i2c_transfer, msg is controlled by user. When msg[i].buf is null and msg[i].len is zero, former checks on msg[i].buf would be passed. Malicious data finally reach dw2102_i2c_transfer. If accessing msg[i].buf[0] without sanity check, null ptr deref would happen. We add check on msg[i].len to prevent crash.

Similar commit: commit 950e252cb469 ("[media] dw2102: limit messages to buffer size")(CVE-2023-53146)

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

fs/jfs: Prevent integer overflow in AG size calculation

The JFS filesystem calculates allocation group (AG) size using 1 << l2agsize in dbExtendFS(). When l2agsize exceeds 31 (possible with >2TB aggregates on 32-bit systems), this 32-bit shift operation causes undefined behavior and improper AG sizing.

On 32-bit architectures: - Left-shifting 1 by 32+ bits results in 0 due to integer overflow - This creates invalid AG sizes (0 or garbage values) in sbi->bmap->db_agsize - Subsequent block allocations would reference invalid AG structures - Could lead to: - Filesystem corruption during extend operations - Kernel crashes due to invalid memory accesses - Security vulnerabilities via malformed on-disk structures

Fix by casting to s64 before shifting: bmp->db_agsize = (s64)1 << l2agsize;

This ensures 64-bit arithmetic even on 32-bit architectures. The cast matches the data type of db_agsize (s64) and follows similar patterns in JFS block calculation code.

Found by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37858)

Severity
5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
References
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "aarch64": [
          "bpftool-4.19.90-2506.1.0.0330.oe2003sp4.aarch64.rpm",
          "bpftool-debuginfo-4.19.90-2506.1.0.0330.oe2003sp4.aarch64.rpm",
          "kernel-4.19.90-2506.1.0.0330.oe2003sp4.aarch64.rpm",
          "kernel-debuginfo-4.19.90-2506.1.0.0330.oe2003sp4.aarch64.rpm",
          "kernel-debugsource-4.19.90-2506.1.0.0330.oe2003sp4.aarch64.rpm",
          "kernel-devel-4.19.90-2506.1.0.0330.oe2003sp4.aarch64.rpm",
          "kernel-source-4.19.90-2506.1.0.0330.oe2003sp4.aarch64.rpm",
          "kernel-tools-4.19.90-2506.1.0.0330.oe2003sp4.aarch64.rpm",
          "kernel-tools-debuginfo-4.19.90-2506.1.0.0330.oe2003sp4.aarch64.rpm",
          "kernel-tools-devel-4.19.90-2506.1.0.0330.oe2003sp4.aarch64.rpm",
          "perf-4.19.90-2506.1.0.0330.oe2003sp4.aarch64.rpm",
          "perf-debuginfo-4.19.90-2506.1.0.0330.oe2003sp4.aarch64.rpm",
          "python2-perf-4.19.90-2506.1.0.0330.oe2003sp4.aarch64.rpm",
          "python2-perf-debuginfo-4.19.90-2506.1.0.0330.oe2003sp4.aarch64.rpm",
          "python3-perf-4.19.90-2506.1.0.0330.oe2003sp4.aarch64.rpm",
          "python3-perf-debuginfo-4.19.90-2506.1.0.0330.oe2003sp4.aarch64.rpm"
        ],
        "src": [
          "kernel-4.19.90-2506.1.0.0330.oe2003sp4.src.rpm"
        ],
        "x86_64": [
          "bpftool-4.19.90-2506.1.0.0330.oe2003sp4.x86_64.rpm",
          "bpftool-debuginfo-4.19.90-2506.1.0.0330.oe2003sp4.x86_64.rpm",
          "kernel-4.19.90-2506.1.0.0330.oe2003sp4.x86_64.rpm",
          "kernel-debuginfo-4.19.90-2506.1.0.0330.oe2003sp4.x86_64.rpm",
          "kernel-debugsource-4.19.90-2506.1.0.0330.oe2003sp4.x86_64.rpm",
          "kernel-devel-4.19.90-2506.1.0.0330.oe2003sp4.x86_64.rpm",
          "kernel-source-4.19.90-2506.1.0.0330.oe2003sp4.x86_64.rpm",
          "kernel-tools-4.19.90-2506.1.0.0330.oe2003sp4.x86_64.rpm",
          "kernel-tools-debuginfo-4.19.90-2506.1.0.0330.oe2003sp4.x86_64.rpm",
          "kernel-tools-devel-4.19.90-2506.1.0.0330.oe2003sp4.x86_64.rpm",
          "perf-4.19.90-2506.1.0.0330.oe2003sp4.x86_64.rpm",
          "perf-debuginfo-4.19.90-2506.1.0.0330.oe2003sp4.x86_64.rpm",
          "python2-perf-4.19.90-2506.1.0.0330.oe2003sp4.x86_64.rpm",
          "python2-perf-debuginfo-4.19.90-2506.1.0.0330.oe2003sp4.x86_64.rpm",
          "python3-perf-4.19.90-2506.1.0.0330.oe2003sp4.x86_64.rpm",
          "python3-perf-debuginfo-4.19.90-2506.1.0.0330.oe2003sp4.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:20.03-LTS-SP4",
        "name": "kernel",
        "purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-20.03-LTS-SP4"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.19.90-2506.1.0.0330.oe2003sp4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "severity": "Medium"
  },
  "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\nmmc: sdhci-pci: Fix possible memory leak caused by missing pci_dev_put()\n\npci_get_device() will increase the reference count for the returned\npci_dev. We need to use pci_dev_put() to decrease the reference count\nbefore amd_probe() returns. There is no problem for the \u0026apos;smbus_dev ==\nNULL\u0026apos; branch because pci_dev_put() can also handle the NULL input\nparameter case.(CVE-2022-49787)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: dw2102: Fix null-ptr-deref in dw2102_i2c_transfer()\n\nIn dw2102_i2c_transfer, msg is controlled by user. When msg[i].buf\nis null and msg[i].len is zero, former checks on msg[i].buf would be\npassed. Malicious data finally reach dw2102_i2c_transfer. If accessing\nmsg[i].buf[0] without sanity check, null ptr deref would happen.\nWe add check on msg[i].len to prevent crash.\n\nSimilar commit:\ncommit 950e252cb469\n(\u0026quot;[media] dw2102: limit messages to buffer size\u0026quot;)(CVE-2023-53146)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/jfs: Prevent integer overflow in AG size calculation\n\nThe JFS filesystem calculates allocation group (AG) size using 1 \u0026lt;\u0026lt;\nl2agsize in dbExtendFS(). When l2agsize exceeds 31 (possible with \u0026gt;2TB\naggregates on 32-bit systems), this 32-bit shift operation causes undefined\nbehavior and improper AG sizing.\n\nOn 32-bit architectures:\n- Left-shifting 1 by 32+ bits results in 0 due to integer overflow\n- This creates invalid AG sizes (0 or garbage values) in\nsbi-\u0026gt;bmap-\u0026gt;db_agsize\n- Subsequent block allocations would reference invalid AG structures\n- Could lead to:\n  - Filesystem corruption during extend operations\n  - Kernel crashes due to invalid memory accesses\n  - Security vulnerabilities via malformed on-disk structures\n\nFix by casting to s64 before shifting:\nbmp-\u0026gt;db_agsize = (s64)1 \u0026lt;\u0026lt; l2agsize;\n\nThis ensures 64-bit arithmetic even on 32-bit architectures. The cast\nmatches the data type of db_agsize (s64) and follows similar patterns in\nJFS block calculation code.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37858)",
  "id": "OESA-2025-1596",
  "modified": "2026-08-06T11:08:41Z",
  "published": "2025-06-06T11:08:41Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-1596"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49787"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-53146"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-37858"
    }
  ],
  "schema_version": "1.7.2",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "kernel security update",
  "upstream": [
    "CVE-2022-49787",
    "CVE-2023-53146",
    "CVE-2025-37858"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.


Detection rules are retrieved from Rulezet.


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.