{
  "cveId": "CVE-2022-50428",
  "url": "https://patchblox.com/security/cve/CVE-2022-50428",
  "summary": "CVE-2022-50428 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-50428, released October 1, 2025. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  ext4: fix off-by-one errors in fast-commit block...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  ext4: fix off-by-one errors in fast-commit block filling  Due to several different off-by-one errors, or perhaps due to a late change in design that wasn\u0027t fully reflected in the code that was actually merged, there are several very strange constraints on how fast-commit blocks are filled with tlv entries:  - tlvs must start at least 10 bytes before the end of the block, even   though the minimum tlv length is 8.  Otherwise, the replay code will   ignore them.  (BUG: ext4_fc_reserve_space() could violate this   requirement if called with a len of blocksize - 9 or blocksize - 8.   Fortunately, this doesn\u0027t seem to happen currently.)  - tlvs must end at least 1 byte before the end of the block.  Otherwise   the replay code will consider them to be invalid.  This quirk   contributed to a bug (fixed by an earlier commit) where uninitialized   memory was being leaked to disk in the last byte of blocks.  Also, strangely these constraints don\u0027t apply to the replay code in e2fsprogs, which will accept any tlvs in the blocks (with no bounds checks at all, but that is a separate issue...).  Given that this all seems to be a bug, let\u0027s fix it by just filling blocks with tlv entries in the natural way.  Note that old kernels will be unable to replay fast-commit journals created by kernels that have this commit.",
  "published": "2025-10-01T12:15:34Z",
  "severity": "medium",
  "cvss": 5.5,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.00159,
  "epssPercentile": 0.05075,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.1.4-1",
      "fix": "DEBIAN-CVE-2022-50428",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50428",
      "released": "2025-10-01T12:15:34Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.1.4-1",
      "fix": "DEBIAN-CVE-2022-50428",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50428",
      "released": "2025-10-01T12:15:34Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.1.4-1",
      "fix": "DEBIAN-CVE-2022-50428",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50428",
      "released": "2025-10-01T12:15:34Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T00:53:09Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}