CVE-2024-50191 (GCVE-0-2024-50191)

Vulnerability from cvelistv5 – Published: 2024-11-08 05:43 – Updated: 2026-05-11 20:47

Title

ext4: don't set SB_RDONLY after filesystem errors

Summary

In the Linux kernel, the following vulnerability has been resolved: ext4: don't set SB_RDONLY after filesystem errors When the filesystem is mounted with errors=remount-ro, we were setting SB_RDONLY flag to stop all filesystem modifications. We knew this misses proper locking (sb->s_umount) and does not go through proper filesystem remount procedure but it has been the way this worked since early ext2 days and it was good enough for catastrophic situation damage mitigation. Recently, syzbot has found a way (see link) to trigger warnings in filesystem freezing because the code got confused by SB_RDONLY changing under its hands. Since these days we set EXT4_FLAGS_SHUTDOWN on the superblock which is enough to stop all filesystem modifications, modifying SB_RDONLY shouldn't be needed. So stop doing that.

Severity

5.5 (Medium)


                        
                          CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

SSVC

Exploitation: none Automatable: no Technical Impact: partial

CISA Coordinator · CISA-ADP (v2.0.3)

Decision recorded 2025-10-01 20:18 UTC

CWE

CWE-noinfo Not enough information

Assigner

Linux mitre root

References

4 references

URL	Tags
https://git.kernel.org/stable/c/58c0648e4c773f5b5…
https://git.kernel.org/stable/c/ee77c388469116565…
https://git.kernel.org/stable/c/d3476f3dad4ad68ae…
https://lists.debian.org/debian-lts-announce/2025…

Impacted products

2 products

Vendor	Product	Version	CPE status
Linux	Linux	Affected: 95257987a6387f02970eda707e55a06cce734e18 , < 58c0648e4c773f5b54f0cb63bc8c7c6bf52719a9 (git) Affected: 95257987a6387f02970eda707e55a06cce734e18 , < ee77c388469116565e009eaa704a60bc78489e09 (git) Affected: 95257987a6387f02970eda707e55a06cce734e18 , < d3476f3dad4ad68ae5f6b008ea6591d1520da5d8 (git)	guessed
Linux	Linux	Affected: 6.6 Unaffected: 0 , < 6.6 (semver) Unaffected: 6.6.57 , ≤ 6.6.* (semver) Unaffected: 6.11.4 , ≤ 6.11.* (semver) Unaffected: 6.12 , ≤ * (original_commit_for_fix)	guessed

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "LOW",
              "attackVector": "LOCAL",
              "availabilityImpact": "HIGH",
              "baseScore": 5.5,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2024-50191",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2025-10-01T20:18:18.496459Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "problemTypes": [
          {
            "descriptions": [
              {
                "description": "CWE-noinfo Not enough information",
                "lang": "en",
                "type": "CWE"
              }
            ]
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2025-10-01T20:27:08.441Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2025-11-03T22:26:44.672Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/ext4/super.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "58c0648e4c773f5b54f0cb63bc8c7c6bf52719a9",
              "status": "affected",
              "version": "95257987a6387f02970eda707e55a06cce734e18",
              "versionType": "git"
            },
            {
              "lessThan": "ee77c388469116565e009eaa704a60bc78489e09",
              "status": "affected",
              "version": "95257987a6387f02970eda707e55a06cce734e18",
              "versionType": "git"
            },
            {
              "lessThan": "d3476f3dad4ad68ae5f6b008ea6591d1520da5d8",
              "status": "affected",
              "version": "95257987a6387f02970eda707e55a06cce734e18",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/ext4/super.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.6"
            },
            {
              "lessThan": "6.6",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.57",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.11.*",
              "status": "unaffected",
              "version": "6.11.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.12",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.57",
                  "versionStartIncluding": "6.6",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.11.4",
                  "versionStartIncluding": "6.6",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12",
                  "versionStartIncluding": "6.6",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\next4: don\u0027t set SB_RDONLY after filesystem errors\n\nWhen the filesystem is mounted with errors=remount-ro, we were setting\nSB_RDONLY flag to stop all filesystem modifications. We knew this misses\nproper locking (sb-\u003es_umount) and does not go through proper filesystem\nremount procedure but it has been the way this worked since early ext2\ndays and it was good enough for catastrophic situation damage\nmitigation. Recently, syzbot has found a way (see link) to trigger\nwarnings in filesystem freezing because the code got confused by\nSB_RDONLY changing under its hands. Since these days we set\nEXT4_FLAGS_SHUTDOWN on the superblock which is enough to stop all\nfilesystem modifications, modifying SB_RDONLY shouldn\u0027t be needed. So\nstop doing that."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-11T20:47:11.359Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/58c0648e4c773f5b54f0cb63bc8c7c6bf52719a9"
        },
        {
          "url": "https://git.kernel.org/stable/c/ee77c388469116565e009eaa704a60bc78489e09"
        },
        {
          "url": "https://git.kernel.org/stable/c/d3476f3dad4ad68ae5f6b008ea6591d1520da5d8"
        }
      ],
      "title": "ext4: don\u0027t set SB_RDONLY after filesystem errors",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-50191",
    "datePublished": "2024-11-08T05:43:47.840Z",
    "dateReserved": "2024-10-21T19:36:19.967Z",
    "dateUpdated": "2026-05-11T20:47:11.359Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2024-50191",
      "date": "2026-09-19",
      "epss": "0.00206",
      "percentile": "0.11047"
    },
    "fkie_nvd": {
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "matchCriteriaId": "F032D82B-5582-4DF5-B921-BFE0BD301364",
                  "versionEndExcluding": "5.15.168",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "matchCriteriaId": "D01BD22E-ACD1-4618-9D01-6116570BE1EE",
                  "versionEndExcluding": "6.1.113",
                  "versionStartIncluding": "5.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "matchCriteriaId": "05D83DB8-7465-4F88-AFB2-980011992AC1",
                  "versionEndExcluding": "6.6.57",
                  "versionStartIncluding": "6.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "matchCriteriaId": "AA84D336-CE9A-4535-B901-1AD77EC17C34",
                  "versionEndExcluding": "6.11.4",
                  "versionStartIncluding": "6.7",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\next4: don\u0027t set SB_RDONLY after filesystem errors\n\nWhen the filesystem is mounted with errors=remount-ro, we were setting\nSB_RDONLY flag to stop all filesystem modifications. We knew this misses\nproper locking (sb-\u003es_umount) and does not go through proper filesystem\nremount procedure but it has been the way this worked since early ext2\ndays and it was good enough for catastrophic situation damage\nmitigation. Recently, syzbot has found a way (see link) to trigger\nwarnings in filesystem freezing because the code got confused by\nSB_RDONLY changing under its hands. Since these days we set\nEXT4_FLAGS_SHUTDOWN on the superblock which is enough to stop all\nfilesystem modifications, modifying SB_RDONLY shouldn\u0027t be needed. So\nstop doing that."
        },
        {
          "lang": "es",
          "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ext4: no establecer SB_RDONLY despu\u00e9s de errores del sistema de archivos Cuando el sistema de archivos se monta con errors=remount-ro, est\u00e1bamos estableciendo el indicador SB_RDONLY para detener todas las modificaciones del sistema de archivos. Sab\u00edamos que esto omite el bloqueo adecuado (sb-\u0026gt;s_umount) y no pasa por el procedimiento de remontaje del sistema de archivos adecuado, pero ha sido la forma en que funcion\u00f3 desde los primeros d\u00edas de ext2 y fue lo suficientemente bueno para la mitigaci\u00f3n de da\u00f1os en situaciones catastr\u00f3ficas. Recientemente, syzbot encontr\u00f3 una forma (ver enlace) de activar advertencias en el congelamiento del sistema de archivos porque el c\u00f3digo se confundi\u00f3 con SB_RDONLY cambiando bajo sus manos. Desde estos d\u00edas establecemos EXT4_FLAGS_SHUTDOWN en el superbloque, lo cual es suficiente para detener todas las modificaciones del sistema de archivos, no deber\u00eda ser necesario modificar SB_RDONLY. As\u00ed que deje de hacer eso."
        }
      ],
      "id": "CVE-2024-50191",
      "lastModified": "2024-12-11T15:36:27.330",
      "metrics": {
        "cvssMetricV31": [
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "LOCAL",
              "availabilityImpact": "HIGH",
              "baseScore": 5.5,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
              "version": "3.1"
            },
            "exploitabilityScore": 1.8,
            "impactScore": 3.6,
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ]
      },
      "published": "2024-11-08T06:15:16.027",
      "references": [
        {
          "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
          "tags": [
            "Patch"
          ],
          "url": "https://git.kernel.org/stable/c/4061e07f040a091f694f461b86a26cf95ae66439"
        },
        {
          "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
          "tags": [
            "Patch"
          ],
          "url": "https://git.kernel.org/stable/c/58c0648e4c773f5b54f0cb63bc8c7c6bf52719a9"
        },
        {
          "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
          "tags": [
            "Patch"
          ],
          "url": "https://git.kernel.org/stable/c/d3476f3dad4ad68ae5f6b008ea6591d1520da5d8"
        },
        {
          "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
          "tags": [
            "Patch"
          ],
          "url": "https://git.kernel.org/stable/c/ee77c388469116565e009eaa704a60bc78489e09"
        },
        {
          "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
          "tags": [
            "Patch"
          ],
          "url": "https://git.kernel.org/stable/c/fbb177bc1d6487cd3e9b50ae0be2781b7297980d"
        }
      ],
      "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "vulnStatus": "Analyzed",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "NVD-CWE-noinfo"
            }
          ],
          "source": "nvd@nist.gov",
          "type": "Primary"
        }
      ]
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Linux",
                "programFiles": [
                  "fs/ext4/super.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "lessThan": "58c0648e4c773f5b54f0cb63bc8c7c6bf52719a9",
                    "status": "affected",
                    "version": "95257987a6387f02970eda707e55a06cce734e18",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "ee77c388469116565e009eaa704a60bc78489e09",
                    "status": "affected",
                    "version": "95257987a6387f02970eda707e55a06cce734e18",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "d3476f3dad4ad68ae5f6b008ea6591d1520da5d8",
                    "status": "affected",
                    "version": "95257987a6387f02970eda707e55a06cce734e18",
                    "versionType": "git"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "product": "Linux",
                "programFiles": [
                  "fs/ext4/super.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "status": "affected",
                    "version": "6.6"
                  },
                  {
                    "lessThan": "6.6",
                    "status": "unaffected",
                    "version": "0",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "6.6.*",
                    "status": "unaffected",
                    "version": "6.6.57",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "6.11.*",
                    "status": "unaffected",
                    "version": "6.11.4",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "*",
                    "status": "unaffected",
                    "version": "6.12",
                    "versionType": "original_commit_for_fix"
                  }
                ]
              }
            ],
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
          }
        ],
        "configurations": [
          {
            "nodes": [
              {
                "cpeMatch": [
                  {
                    "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                    "matchCriteriaId": "F032D82B-5582-4DF5-B921-BFE0BD301364",
                    "versionEndExcluding": "5.15.168",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                    "matchCriteriaId": "D01BD22E-ACD1-4618-9D01-6116570BE1EE",
                    "versionEndExcluding": "6.1.113",
                    "versionStartIncluding": "5.16",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                    "matchCriteriaId": "05D83DB8-7465-4F88-AFB2-980011992AC1",
                    "versionEndExcluding": "6.6.57",
                    "versionStartIncluding": "6.2",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                    "matchCriteriaId": "AA84D336-CE9A-4535-B901-1AD77EC17C34",
                    "versionEndExcluding": "6.11.4",
                    "versionStartIncluding": "6.7",
                    "vulnerable": true
                  }
                ],
                "negate": false,
                "operator": "OR"
              }
            ]
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "In the Linux kernel, the following vulnerability has been resolved:\n\next4: don\u0027t set SB_RDONLY after filesystem errors\n\nWhen the filesystem is mounted with errors=remount-ro, we were setting\nSB_RDONLY flag to stop all filesystem modifications. We knew this misses\nproper locking (sb-\u003es_umount) and does not go through proper filesystem\nremount procedure but it has been the way this worked since early ext2\ndays and it was good enough for catastrophic situation damage\nmitigation. Recently, syzbot has found a way (see link) to trigger\nwarnings in filesystem freezing because the code got confused by\nSB_RDONLY changing under its hands. Since these days we set\nEXT4_FLAGS_SHUTDOWN on the superblock which is enough to stop all\nfilesystem modifications, modifying SB_RDONLY shouldn\u0027t be needed. So\nstop doing that."
          },
          {
            "lang": "es",
            "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ext4: no establecer SB_RDONLY despu\u00e9s de errores del sistema de archivos Cuando el sistema de archivos se monta con errors=remount-ro, est\u00e1bamos estableciendo el indicador SB_RDONLY para detener todas las modificaciones del sistema de archivos. Sab\u00edamos que esto omite el bloqueo adecuado (sb-\u0026gt;s_umount) y no pasa por el procedimiento de remontaje del sistema de archivos adecuado, pero ha sido la forma en que funcion\u00f3 desde los primeros d\u00edas de ext2 y fue lo suficientemente bueno para la mitigaci\u00f3n de da\u00f1os en situaciones catastr\u00f3ficas. Recientemente, syzbot encontr\u00f3 una forma (ver enlace) de activar advertencias en el congelamiento del sistema de archivos porque el c\u00f3digo se confundi\u00f3 con SB_RDONLY cambiando bajo sus manos. Desde estos d\u00edas establecemos EXT4_FLAGS_SHUTDOWN en el superbloque, lo cual es suficiente para detener todas las modificaciones del sistema de archivos, no deber\u00eda ser necesario modificar SB_RDONLY. As\u00ed que deje de hacer eso."
          }
        ],
        "id": "CVE-2024-50191",
        "lastModified": "2026-06-17T08:03:49.910",
        "metrics": {
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "LOCAL",
                "availabilityImpact": "HIGH",
                "baseScore": 5.5,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "LOW",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
                "version": "3.1"
              },
              "exploitabilityScore": 1.8,
              "impactScore": 3.6,
              "source": "nvd@nist.gov",
              "type": "Primary"
            },
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "LOCAL",
                "availabilityImpact": "HIGH",
                "baseScore": 5.5,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "LOW",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
                "version": "3.1"
              },
              "exploitabilityScore": 1.8,
              "impactScore": 3.6,
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "type": "Secondary"
            }
          ],
          "ssvcV203": [
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2024-50191",
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "no"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2025-10-01T20:18:18.496459Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2024-11-08T06:15:16.027",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "tags": [
              "Patch"
            ],
            "url": "https://git.kernel.org/stable/c/58c0648e4c773f5b54f0cb63bc8c7c6bf52719a9"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "tags": [
              "Patch"
            ],
            "url": "https://git.kernel.org/stable/c/d3476f3dad4ad68ae5f6b008ea6591d1520da5d8"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "tags": [
              "Patch"
            ],
            "url": "https://git.kernel.org/stable/c/ee77c388469116565e009eaa704a60bc78489e09"
          },
          {
            "source": "af854a3a-2127-422b-91ae-364da2661108",
            "url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Modified",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "NVD-CWE-noinfo"
              }
            ],
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ]
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-09-14T11:56:15+00:00",
      "cve": "CVE-2024-50191",
      "id": "CVE-2024-50191",
      "initial_release_date": "2024-11-08T00:00:00+00:00",
      "product_status:fixed": "305",
      "product_status:known_affected": "112",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: ext4: don\u0026#39;t set SB_RDONLY after filesystem errors",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-50191.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-09-11T02:11:03Z",
      "cve": "CVE-2024-50191",
      "id": "CVE-2024-50191",
      "initial_release_date": "2024-11-09T03:48:56Z",
      "product_status:known_affected": "187",
      "product_status:recommended": "49",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2024-50191",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2024-50191.json",
      "version": "40"
    },
    "vulnrichment": {
      "containers": {
        "adp": [
          {
            "providerMetadata": {
              "dateUpdated": "2025-11-03T22:26:44.672Z",
              "orgId": "af854a3a-2127-422b-91ae-364da2661108",
              "shortName": "CVE"
            },
            "references": [
              {
                "url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
              }
            ],
            "title": "CVE Program Container"
          },
          {
            "metrics": [
              {
                "cvssV3_1": {
                  "attackComplexity": "LOW",
                  "attackVector": "LOCAL",
                  "availabilityImpact": "HIGH",
                  "baseScore": 5.5,
                  "baseSeverity": "MEDIUM",
                  "confidentialityImpact": "NONE",
                  "integrityImpact": "NONE",
                  "privilegesRequired": "LOW",
                  "scope": "UNCHANGED",
                  "userInteraction": "NONE",
                  "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
                  "version": "3.1"
                }
              },
              {
                "other": {
                  "content": {
                    "id": "CVE-2024-50191",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2025-10-01T20:18:18.496459Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "problemTypes": [
              {
                "descriptions": [
                  {
                    "description": "CWE-noinfo Not enough information",
                    "lang": "en",
                    "type": "CWE"
                  }
                ]
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2025-10-01T15:21:03.312Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "defaultStatus": "unaffected",
              "product": "Linux",
              "programFiles": [
                "fs/ext4/super.c"
              ],
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "vendor": "Linux",
              "versions": [
                {
                  "lessThan": "58c0648e4c773f5b54f0cb63bc8c7c6bf52719a9",
                  "status": "affected",
                  "version": "95257987a6387f02970eda707e55a06cce734e18",
                  "versionType": "git"
                },
                {
                  "lessThan": "ee77c388469116565e009eaa704a60bc78489e09",
                  "status": "affected",
                  "version": "95257987a6387f02970eda707e55a06cce734e18",
                  "versionType": "git"
                },
                {
                  "lessThan": "d3476f3dad4ad68ae5f6b008ea6591d1520da5d8",
                  "status": "affected",
                  "version": "95257987a6387f02970eda707e55a06cce734e18",
                  "versionType": "git"
                }
              ]
            },
            {
              "defaultStatus": "affected",
              "product": "Linux",
              "programFiles": [
                "fs/ext4/super.c"
              ],
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "vendor": "Linux",
              "versions": [
                {
                  "status": "affected",
                  "version": "6.6"
                },
                {
                  "lessThan": "6.6",
                  "status": "unaffected",
                  "version": "0",
                  "versionType": "semver"
                },
                {
                  "lessThanOrEqual": "6.6.*",
                  "status": "unaffected",
                  "version": "6.6.57",
                  "versionType": "semver"
                },
                {
                  "lessThanOrEqual": "6.11.*",
                  "status": "unaffected",
                  "version": "6.11.4",
                  "versionType": "semver"
                },
                {
                  "lessThanOrEqual": "*",
                  "status": "unaffected",
                  "version": "6.12",
                  "versionType": "original_commit_for_fix"
                }
              ]
            }
          ],
          "cpeApplicability": [
            {
              "nodes": [
                {
                  "cpeMatch": [
                    {
                      "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                      "versionEndExcluding": "6.6.57",
                      "versionStartIncluding": "6.6",
                      "vulnerable": true
                    },
                    {
                      "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                      "versionEndExcluding": "6.11.4",
                      "versionStartIncluding": "6.6",
                      "vulnerable": true
                    },
                    {
                      "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                      "versionEndExcluding": "6.12",
                      "versionStartIncluding": "6.6",
                      "vulnerable": true
                    }
                  ],
                  "negate": false,
                  "operator": "OR"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "In the Linux kernel, the following vulnerability has been resolved:\n\next4: don\u0027t set SB_RDONLY after filesystem errors\n\nWhen the filesystem is mounted with errors=remount-ro, we were setting\nSB_RDONLY flag to stop all filesystem modifications. We knew this misses\nproper locking (sb-\u003es_umount) and does not go through proper filesystem\nremount procedure but it has been the way this worked since early ext2\ndays and it was good enough for catastrophic situation damage\nmitigation. Recently, syzbot has found a way (see link) to trigger\nwarnings in filesystem freezing because the code got confused by\nSB_RDONLY changing under its hands. Since these days we set\nEXT4_FLAGS_SHUTDOWN on the superblock which is enough to stop all\nfilesystem modifications, modifying SB_RDONLY shouldn\u0027t be needed. So\nstop doing that."
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-01-05T10:55:15.999Z",
            "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "shortName": "Linux"
          },
          "references": [
            {
              "url": "https://git.kernel.org/stable/c/58c0648e4c773f5b54f0cb63bc8c7c6bf52719a9"
            },
            {
              "url": "https://git.kernel.org/stable/c/ee77c388469116565e009eaa704a60bc78489e09"
            },
            {
              "url": "https://git.kernel.org/stable/c/d3476f3dad4ad68ae5f6b008ea6591d1520da5d8"
            }
          ],
          "title": "ext4: don\u0027t set SB_RDONLY after filesystem errors",
          "x_generator": {
            "engine": "bippy-1.2.0"
          }
        }
      },
      "cveMetadata": {
        "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "assignerShortName": "Linux",
        "cveId": "CVE-2024-50191",
        "datePublished": "2024-11-08T05:43:47.840Z",
        "dateReserved": "2024-10-21T19:36:19.967Z",
        "dateUpdated": "2026-01-05T10:55:15.999Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}

CERTFR-2025-AVI-0349

Vulnerability from certfr_avis - Published: - Updated:

De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, une élévation de privilèges et une atteinte à la confidentialité des données

Solutions

Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).

Impacted products

Vendor	Product	Description
Ubuntu	Ubuntu	Ubuntu 24.04 LTS
Ubuntu	Ubuntu	Ubuntu 18.04 ESM
Ubuntu	Ubuntu	Ubuntu 20.04 LTS
Ubuntu	Ubuntu	Ubuntu 24.10
Ubuntu	Ubuntu	Ubuntu 22.04 LTS

References

Title

Publication Time

CERTFR-2025-AVI-0366

Vulnerability from certfr_avis - Published: - Updated:

De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une élévation de privilèges et une atteinte à la confidentialité des données.

Solutions

Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).

Impacted products

	Vendor	Product	Description
	Ubuntu	Ubuntu	Ubuntu 24.04 LTS
	Ubuntu	Ubuntu	Ubuntu 20.04 LTS

References

Title

Publication Time

FKIE_CVE-2024-50191

Vulnerability from fkie_nvd - Published: 2024-11-08 06:15 - Updated: 2026-06-17 08:03

Severity

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

Summary

References

URL	Tags
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/58c0648e4c773f5b54f0cb63bc8c7c6bf52719a9	Patch
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/d3476f3dad4ad68ae5f6b008ea6591d1520da5d8	Patch
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/ee77c388469116565e009eaa704a60bc78489e09	Patch
af854a3a-2127-422b-91ae-364da2661108	https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html

Impacted products

Vendor	Product	Version
linux	linux_kernel	*
linux	linux_kernel	*
linux	linux_kernel	*
linux	linux_kernel	*

JSON

To clipboard

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/ext4/super.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "58c0648e4c773f5b54f0cb63bc8c7c6bf52719a9",
              "status": "affected",
              "version": "95257987a6387f02970eda707e55a06cce734e18",
              "versionType": "git"
            },
            {
              "lessThan": "ee77c388469116565e009eaa704a60bc78489e09",
              "status": "affected",
              "version": "95257987a6387f02970eda707e55a06cce734e18",
              "versionType": "git"
            },
            {
              "lessThan": "d3476f3dad4ad68ae5f6b008ea6591d1520da5d8",
              "status": "affected",
              "version": "95257987a6387f02970eda707e55a06cce734e18",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/ext4/super.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.6"
            },
            {
              "lessThan": "6.6",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.57",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.11.*",
              "status": "unaffected",
              "version": "6.11.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.12",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "F032D82B-5582-4DF5-B921-BFE0BD301364",
              "versionEndExcluding": "5.15.168",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "D01BD22E-ACD1-4618-9D01-6116570BE1EE",
              "versionEndExcluding": "6.1.113",
              "versionStartIncluding": "5.16",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "05D83DB8-7465-4F88-AFB2-980011992AC1",
              "versionEndExcluding": "6.6.57",
              "versionStartIncluding": "6.2",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "AA84D336-CE9A-4535-B901-1AD77EC17C34",
              "versionEndExcluding": "6.11.4",
              "versionStartIncluding": "6.7",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\next4: don\u0027t set SB_RDONLY after filesystem errors\n\nWhen the filesystem is mounted with errors=remount-ro, we were setting\nSB_RDONLY flag to stop all filesystem modifications. We knew this misses\nproper locking (sb-\u003es_umount) and does not go through proper filesystem\nremount procedure but it has been the way this worked since early ext2\ndays and it was good enough for catastrophic situation damage\nmitigation. Recently, syzbot has found a way (see link) to trigger\nwarnings in filesystem freezing because the code got confused by\nSB_RDONLY changing under its hands. Since these days we set\nEXT4_FLAGS_SHUTDOWN on the superblock which is enough to stop all\nfilesystem modifications, modifying SB_RDONLY shouldn\u0027t be needed. So\nstop doing that."
    },
    {
      "lang": "es",
      "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ext4: no establecer SB_RDONLY despu\u00e9s de errores del sistema de archivos Cuando el sistema de archivos se monta con errors=remount-ro, est\u00e1bamos estableciendo el indicador SB_RDONLY para detener todas las modificaciones del sistema de archivos. Sab\u00edamos que esto omite el bloqueo adecuado (sb-\u0026gt;s_umount) y no pasa por el procedimiento de remontaje del sistema de archivos adecuado, pero ha sido la forma en que funcion\u00f3 desde los primeros d\u00edas de ext2 y fue lo suficientemente bueno para la mitigaci\u00f3n de da\u00f1os en situaciones catastr\u00f3ficas. Recientemente, syzbot encontr\u00f3 una forma (ver enlace) de activar advertencias en el congelamiento del sistema de archivos porque el c\u00f3digo se confundi\u00f3 con SB_RDONLY cambiando bajo sus manos. Desde estos d\u00edas establecemos EXT4_FLAGS_SHUTDOWN en el superbloque, lo cual es suficiente para detener todas las modificaciones del sistema de archivos, no deber\u00eda ser necesario modificar SB_RDONLY. As\u00ed que deje de hacer eso."
    }
  ],
  "id": "CVE-2024-50191",
  "lastModified": "2026-06-17T08:03:49.910",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "LOCAL",
          "availabilityImpact": "HIGH",
          "baseScore": 5.5,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "NONE",
          "integrityImpact": "NONE",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 1.8,
        "impactScore": 3.6,
        "source": "nvd@nist.gov",
        "type": "Primary"
      },
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "LOCAL",
          "availabilityImpact": "HIGH",
          "baseScore": 5.5,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "NONE",
          "integrityImpact": "NONE",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 1.8,
        "impactScore": 3.6,
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2024-50191",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2025-10-01T20:18:18.496459Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2024-11-08T06:15:16.027",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "tags": [
        "Patch"
      ],
      "url": "https://git.kernel.org/stable/c/58c0648e4c773f5b54f0cb63bc8c7c6bf52719a9"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "tags": [
        "Patch"
      ],
      "url": "https://git.kernel.org/stable/c/d3476f3dad4ad68ae5f6b008ea6591d1520da5d8"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "tags": [
        "Patch"
      ],
      "url": "https://git.kernel.org/stable/c/ee77c388469116565e009eaa704a60bc78489e09"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Modified",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "NVD-CWE-noinfo"
        }
      ],
      "source": "nvd@nist.gov",
      "type": "Primary"
    }
  ]
}

GHSA-639P-PGPG-5QR5

Vulnerability from github – Published: 2024-11-08 06:30 – Updated: 2025-11-04 00:31

Details

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

ext4: don't set SB_RDONLY after filesystem errors

When the filesystem is mounted with errors=remount-ro, we were setting SB_RDONLY flag to stop all filesystem modifications. We knew this misses proper locking (sb->s_umount) and does not go through proper filesystem remount procedure but it has been the way this worked since early ext2 days and it was good enough for catastrophic situation damage mitigation. Recently, syzbot has found a way (see link) to trigger warnings in filesystem freezing because the code got confused by SB_RDONLY changing under its hands. Since these days we set EXT4_FLAGS_SHUTDOWN on the superblock which is enough to stop all filesystem modifications, modifying SB_RDONLY shouldn't be needed. So stop doing that.

Severity

5.5 (Medium)


                  
                    CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2024-50191"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-11-08T06:15:16Z",
    "severity": "MODERATE"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\next4: don\u0027t set SB_RDONLY after filesystem errors\n\nWhen the filesystem is mounted with errors=remount-ro, we were setting\nSB_RDONLY flag to stop all filesystem modifications. We knew this misses\nproper locking (sb-\u003es_umount) and does not go through proper filesystem\nremount procedure but it has been the way this worked since early ext2\ndays and it was good enough for catastrophic situation damage\nmitigation. Recently, syzbot has found a way (see link) to trigger\nwarnings in filesystem freezing because the code got confused by\nSB_RDONLY changing under its hands. Since these days we set\nEXT4_FLAGS_SHUTDOWN on the superblock which is enough to stop all\nfilesystem modifications, modifying SB_RDONLY shouldn\u0027t be needed. So\nstop doing that.",
  "id": "GHSA-639p-pgpg-5qr5",
  "modified": "2025-11-04T00:31:57Z",
  "published": "2024-11-08T06:30:49Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50191"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/4061e07f040a091f694f461b86a26cf95ae66439"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/58c0648e4c773f5b54f0cb63bc8c7c6bf52719a9"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/d3476f3dad4ad68ae5f6b008ea6591d1520da5d8"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/ee77c388469116565e009eaa704a60bc78489e09"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/fbb177bc1d6487cd3e9b50ae0be2781b7297980d"
    },
    {
      "type": "WEB",
      "url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}

OESA-2024-2492 (CVE-2023-52920)

Vulnerability from osv_openeuler – Published: 2024-11-29 11:07 – Updated: 2026-08-06 11:07 – Source website

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: bpf: support non-r10 register spill/fill to/from stack in precision tracking Use instruction (jump) history to record instructions that performed register spill/fill to/from stack, regardless if this was done through read-only r10 register, or any other register after copying r10 into it and potentially adjusting offset. To make this work reliably, we push extra per-instruction flags into instruction history, encoding stack slot index (spi) and stack frame number in extra 10 bit flags we take away from prev_idx in instruction history. We don't touch idx field for maximum performance, as it's checked most frequently during backtracking. This change removes basically the last remaining practical limitation of precision backtracking logic in BPF verifier. It fixes known deficiencies, but also opens up new opportunities to reduce number of verified states, explored in the subsequent patches. There are only three differences in selftests' BPF object files according to veristat, all in the positive direction (less states). File Program Insns (A) Insns (B) Insns (DIFF) States (A) States (B) States (DIFF) -------------------------------------- ------------- --------- --------- ------------- ---------- ---------- ------------- test_cls_redirect_dynptr.bpf.linked3.o cls_redirect 2987 2864 -123 (-4.12%) 240 231 -9 (-3.75%) xdp_synproxy_kern.bpf.linked3.o syncookie_tc 82848 82661 -187 (-0.23%) 5107 5073 -34 (-0.67%) xdp_synproxy_kern.bpf.linked3.o syncookie_xdp 85116 84964 -152 (-0.18%) 5162 5130 -32 (-0.62%) Note, I avoided renaming jmp_history to more generic insn_hist to minimize number of lines changed and potential merge conflicts between bpf and bpf-next trees. Notice also cur_hist_entry pointer reset to NULL at the beginning of instruction verification loop. This pointer avoids the problem of relying on last jump history entry's insn_idx to determine whether we already have entry for current instruction or not. It can happen that we added jump history entry because current instruction is_jmp_point(), but also we need to add instruction flags for stack access. In this case, we don't want to entries, so we need to reuse last added entry, if it is present. Relying on insn_idx comparison has the same ambiguity problem as the one that was fixed recently in [0], so we avoid that. [0] https://patchwork.kernel.org/project/netdevbpf/patch/20231110002638.4168352-3-andrii@kernel.org/(CVE-2023-52920)

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

mptcp: pm: only mark 'subflow' endp as available

Adding the following warning ...

WARN_ON_ONCE(msk->pm.local_addr_used == 0)

... before decrementing the local_addr_used counter helped to find a bug when running the "remove single address" subtest from the mptcp_join.sh selftests.

Removing a 'signal' endpoint will trigger the removal of all subflows linked to this endpoint via mptcp_pm_nl_rm_addr_or_subflow() with rm_type == MPTCP_MIB_RMSUBFLOW. This will decrement the local_addr_used counter, which is wrong in this case because this counter is linked to 'subflow' endpoints, and here it is a 'signal' endpoint that is being removed.

Now, the counter is decremented, only if the ID is being used outside of mptcp_pm_nl_rm_addr_or_subflow(), only for 'subflow' endpoints, and if the ID is not 0 -- local_addr_used is not taking into account these ones. This marking of the ID as being available, and the decrement is done no matter if a subflow using this ID is currently available, because the subflow could have been closed before.(CVE-2024-45010)

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

video/aperture: optionally match the device in sysfb_disable()

In aperture_remove_conflicting_pci_devices(), we currently only call sysfb_disable() on vga class devices. This leads to the following problem when the pimary device is not VGA compatible:

A PCI device with a non-VGA class is the boot display
That device is probed first and it is not a VGA device so sysfb_disable() is not called, but the device resources are freed by aperture_detach_platform_device()
Non-primary GPU has a VGA class and it ends up calling sysfb_disable()
NULL pointer dereference via sysfb_disable() since the resources have already been freed by aperture_detach_platform_device() when it was called by the other device.

Fix this by passing a device pointer to sysfb_disable() and checking the device to determine if we should execute it or not.

v2: Fix build when CONFIG_SCREEN_INFO is not set v3: Move device check into the mutex Drop primary variable in aperture_remove_conflicting_pci_devices() Drop __init on pci sysfb_pci_dev_is_enabled()(CVE-2024-46698)

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

perf/aux: Fix AUX buffer serialization

Ole reported that event->mmap_mutex is strictly insufficient to serialize the AUX buffer, add a per RB mutex to fully serialize it.

Note that in the lock order comment the perf_event::mmap_mutex order was already wrong, that is, it nesting under mmap_lock is not new with this patch.(CVE-2024-46713)

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

ice: protect XDP configuration with a mutex

The main threat to data consistency in ice_xdp() is a possible asynchronous PF reset. It can be triggered by a user or by TX timeout handler.

XDP setup and PF reset code access the same resources in the following sections: * ice_vsi_close() in ice_prepare_for_reset() - already rtnl-locked * ice_vsi_rebuild() for the PF VSI - not protected * ice_vsi_open() - already rtnl-locked

With an unfortunate timing, such accesses can result in a crash such as the one below:

[ +1.999878] ice 0000:b1:00.0: Registered XDP mem model MEM_TYPE_XSK_BUFF_POOL on Rx ring 14 [ +2.002992] ice 0000:b1:00.0: Registered XDP mem model MEM_TYPE_XSK_BUFF_POOL on Rx ring 18 [Mar15 18:17] ice 0000:b1:00.0 ens801f0np0: NETDEV WATCHDOG: CPU: 38: transmit queue 14 timed out 80692736 ms [ +0.000093] ice 0000:b1:00.0 ens801f0np0: tx_timeout: VSI_num: 6, Q 14, NTC: 0x0, HW_HEAD: 0x0, NTU: 0x0, INT: 0x4000001 [ +0.000012] ice 0000:b1:00.0 ens801f0np0: tx_timeout recovery level 1, txqueue 14 [ +0.394718] ice 0000:b1:00.0: PTP reset successful [ +0.006184] BUG: kernel NULL pointer dereference, address: 0000000000000098 [ +0.000045] #PF: supervisor read access in kernel mode [ +0.000023] #PF: error_code(0x0000) - not-present page [ +0.000023] PGD 0 P4D 0 [ +0.000018] Oops: 0000 [#1] PREEMPT SMP NOPTI [ +0.000023] CPU: 38 PID: 7540 Comm: kworker/38:1 Not tainted 6.8.0-rc7 #1 [ +0.000031] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0014.082620210524 08/26/2021 [ +0.000036] Workqueue: ice ice_service_task [ice] [ +0.000183] RIP: 0010:ice_clean_tx_ring+0xa/0xd0 [ice] [...] [ +0.000013] Call Trace: [ +0.000016] <TASK> [ +0.000014] ? __die+0x1f/0x70 [ +0.000029] ? page_fault_oops+0x171/0x4f0 [ +0.000029] ? schedule+0x3b/0xd0 [ +0.000027] ? exc_page_fault+0x7b/0x180 [ +0.000022] ? asm_exc_page_fault+0x22/0x30 [ +0.000031] ? ice_clean_tx_ring+0xa/0xd0 [ice] [ +0.000194] ice_free_tx_ring+0xe/0x60 [ice] [ +0.000186] ice_destroy_xdp_rings+0x157/0x310 [ice] [ +0.000151] ice_vsi_decfg+0x53/0xe0 [ice] [ +0.000180] ice_vsi_rebuild+0x239/0x540 [ice] [ +0.000186] ice_vsi_rebuild_by_type+0x76/0x180 [ice] [ +0.000145] ice_rebuild+0x18c/0x840 [ice] [ +0.000145] ? delay_tsc+0x4a/0xc0 [ +0.000022] ? delay_tsc+0x92/0xc0 [ +0.000020] ice_do_reset+0x140/0x180 [ice] [ +0.000886] ice_service_task+0x404/0x1030 [ice] [ +0.000824] process_one_work+0x171/0x340 [ +0.000685] worker_thread+0x277/0x3a0 [ +0.000675] ? preempt_count_add+0x6a/0xa0 [ +0.000677] ? _raw_spin_lock_irqsave+0x23/0x50 [ +0.000679] ? __pfx_worker_thread+0x10/0x10 [ +0.000653] kthread+0xf0/0x120 [ +0.000635] ? __pfx_kthread+0x10/0x10 [ +0.000616] ret_from_fork+0x2d/0x50 [ +0.000612] ? __pfx_kthread+0x10/0x10 [ +0.000604] ret_from_fork_asm+0x1b/0x30 [ +0.000604] </TASK>

The previous way of handling this through returning -EBUSY is not viable, particularly when destroying AF_XDP socket, because the kernel proceeds with removal anyway.

There is plenty of code between those calls and there is no need to create a large critical section that covers all of them, same as there is no need to protect ice_vsi_rebuild() with rtnl_lock().

Add xdp_state_lock mutex to protect ice_vsi_rebuild() and ice_xdp().

Leaving unprotected sections in between would result in two states that have to be considered: 1. when the VSI is closed, but not yet rebuild 2. when VSI is already rebuild, but not yet open

The latter case is actually already handled through !netif_running() case, we just need to adjust flag checking a little. The former one is not as trivial, because between ice_vsi_close() and ice_vsi_rebuild(), a lot of hardware interaction happens, this can make adding/deleting rings exit with an error. Luckily, VSI rebuild is pending and can apply new configuration for us in a managed fashion.

Therefore, add an additional VSI state flag ICE_VSI_REBUILD_PENDING to indicate that ice_x ---truncated---(CVE-2024-46765)

In the Linux kernel, the following vulnerability has been resolved: icmp: change the order of rate limits ICMP messages are ratelimited : After the blamed commits, the two rate limiters are applied in this order: 1) host wide ratelimit (icmp_global_allow()) 2) Per destination ratelimit (inetpeer based) In order to avoid side-channels attacks, we need to apply the per destination check first. This patch makes the following change : 1) icmp_global_allow() checks if the host wide limit is reached. But credits are not yet consumed. This is deferred to 3) 2) The per destination limit is checked/updated. This might add a new node in inetpeer tree. 3) icmp_global_consume() consumes tokens if prior operations succeeded. This means that host wide ratelimit is still effective in keeping inetpeer tree small even under DDOS. As a bonus, I removed icmp_global.lock as the fast path can use a lock-free operation.(CVE-2024-47678)

In the Linux kernel, the following vulnerability has been resolved: ipv6: avoid possible NULL deref in rt6_uncached_list_flush_dev() Blamed commit accidentally removed a check for rt->rt6i_idev being NULL, as spotted by syzbot: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 1 UID: 0 PID: 10998 Comm: syz-executor Not tainted 6.11.0-rc6-syzkaller-00208-g625403177711 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:rt6_uncached_list_flush_dev net/ipv6/route.c:177 [inline] RIP: 0010:rt6_disable_ip+0x33e/0x7e0 net/ipv6/route.c:4914 Code: 41 80 3c 04 00 74 0a e8 90 d0 9b f7 48 8b 7c 24 08 48 8b 07 48 89 44 24 10 4c 89 f0 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df <80> 3c 08 00 74 08 4c 89 f7 e8 64 d0 9b f7 48 8b 44 24 18 49 39 06 RSP: 0018:ffffc900047374e0 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 1ffff1100fdf8f33 RCX: dffffc0000000000 RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffff88807efc78c0 RBP: ffffc900047375d0 R08: 0000000000000003 R09: fffff520008e6e8c R10: dffffc0000000000 R11: fffff520008e6e8c R12: 1ffff1100fdf8f18 R13: ffff88807efc7998 R14: 0000000000000000 R15: ffff88807efc7930 FS: 0000000000000000(0000) GS:ffff8880b8900000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020002a80 CR3: 0000000022f62000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> addrconf_ifdown+0x15d/0x1bd0 net/ipv6/addrconf.c:3856 addrconf_notify+0x3cb/0x1020 notifier_call_chain+0x19f/0x3e0 kernel/notifier.c:93 call_netdevice_notifiers_extack net/core/dev.c:2032 [inline] call_netdevice_notifiers net/core/dev.c:2046 [inline] unregister_netdevice_many_notify+0xd81/0x1c40 net/core/dev.c:11352 unregister_netdevice_many net/core/dev.c:11414 [inline] unregister_netdevice_queue+0x303/0x370 net/core/dev.c:11289 unregister_netdevice include/linux/netdevice.h:3129 [inline] __tun_detach+0x6b9/0x1600 drivers/net/tun.c:685 tun_detach drivers/net/tun.c:701 [inline] tun_chr_close+0x108/0x1b0 drivers/net/tun.c:3510 __fput+0x24a/0x8a0 fs/file_table.c:422 task_work_run+0x24f/0x310 kernel/task_work.c:228 exit_task_work include/linux/task_work.h:40 [inline] do_exit+0xa2f/0x27f0 kernel/exit.c:882 do_group_exit+0x207/0x2c0 kernel/exit.c:1031 __do_sys_exit_group kernel/exit.c:1042 [inline] __se_sys_exit_group kernel/exit.c:1040 [inline] __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1040 x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f1acc77def9 Code: Unable to access opcode bytes at 0x7f1acc77decf. RSP: 002b:00007ffeb26fa738 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f1acc77def9 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000043 RBP: 00007f1acc7dd508 R08: 00007ffeb26f84d7 R09: 0000000000000003 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001 R13: 0000000000000003 R14: 00000000ffffffff R15: 00007ffeb26fa8e0 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:rt6_uncached_list_flush_dev net/ipv6/route.c:177 [inline] RIP: 0010:rt6_disable_ip+0x33e/0x7e0 net/ipv6/route.c:4914 Code: 41 80 3c 04 00 74 0a e8 90 d0 9b f7 48 8b 7c 24 08 48 8b 07 48 89 44 24 10 4c 89 f0 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df <80> 3c 08 00 74 08 4c 89 f7 e8 64 d0 9b f7 48 8b 44 24 18 49 39 06 RSP: 0018:ffffc900047374e0 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 1ffff1100fdf8f33 RCX: dffffc0000000000 RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffff88807efc78c0 R ---truncated---(CVE-2024-47707)

In the Linux kernel, the following vulnerability has been resolved: wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param In the wilc_parse_join_bss_param function, the TSF field of the ies structure is accessed after the RCU read-side critical section is unlocked. According to RCU usage rules, this is illegal. Reusing this pointer can lead to unpredictable behavior, including accessing memory that has been updated or causing use-after-free issues. This possible bug was identified using a static analysis tool developed by myself, specifically designed to detect RCU-related issues. To address this, the TSF value is now stored in a local variable ies_tsf before the RCU lock is released. The param->tsf_lo field is then assigned using this local variable, ensuring that the TSF value is safely accessed.(CVE-2024-47712)

In the Linux kernel, the following vulnerability has been resolved: mm: call the security_mmap_file() LSM hook in remap_file_pages() The remap_file_pages syscall handler calls do_mmap() directly, which doesn't contain the LSM security check. And if the process has called personality(READ_IMPLIES_EXEC) before and remap_file_pages() is called for RW pages, this will actually result in remapping the pages to RWX, bypassing a W^X policy enforced by SELinux. So we should check prot by security_mmap_file LSM hook in the remap_file_pages syscall handler before do_mmap() is called. Otherwise, it potentially permits an attacker to bypass a W^X policy enforced by SELinux. The bypass is similar to CVE-2016-10044, which bypass the same thing via AIO and can be found in [1]. The PoC: $ cat > test.c int main(void) { size_t pagesz = sysconf(_SC_PAGE_SIZE); int mfd = syscall(SYS_memfd_create, "test", 0); const char *buf = mmap(NULL, 4 * pagesz, PROT_READ | PROT_WRITE, MAP_SHARED, mfd, 0); unsigned int old = syscall(SYS_personality, 0xffffffff); syscall(SYS_personality, READ_IMPLIES_EXEC | old); syscall(SYS_remap_file_pages, buf, pagesz, 0, 2, 0); syscall(SYS_personality, old); // show the RWX page exists even if W^X policy is enforced int fd = open("/proc/self/maps", O_RDONLY); unsigned char buf2[1024]; while (1) { int ret = read(fd, buf2, 1024); if (ret <= 0) break; write(1, buf2, ret); } close(fd); } $ gcc test.c -o test $ ./test | grep rwx 7f1836c34000-7f1836c35000 rwxs 00002000 00:01 2050 /memfd:test (deleted) PM: subject line tweaks

In the Linux kernel, the following vulnerability has been resolved: net: seeq: Fix use after free vulnerability in ether3 Driver Due to Race Condition In the ether3_probe function, a timer is initialized with a callback function ether3_ledoff, bound to &prev(dev)->timer. Once the timer is started, there is a risk of a race condition if the module or device is removed, triggering the ether3_remove function to perform cleanup. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | ether3_ledoff ether3_remove | free_netdev(dev); | put_devic | kfree(dev); | | ether3_outw(priv(dev)->regs.config2 |= CFG2_CTRLO, REG_CONFIG2); | // use dev Fix it by ensuring that the timer is canceled before proceeding with the cleanup in ether3_remove.(CVE-2024-47747)

In the Linux kernel, the following vulnerability has been resolved: RDMA/cxgb4: Added NULL check for lookup_atid The lookup_atid() function can return NULL if the ATID is invalid or does not exist in the identifier table, which could lead to dereferencing a null pointer without a check in the act_establish() and act_open_rpl() functions. Add a NULL check to prevent null pointer dereferencing. Found by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-47749)

In the Linux kernel, the following vulnerability has been resolved: x86/sgx: Fix deadlock in SGX NUMA node search When the current node doesn't have an EPC section configured by firmware and all other EPC sections are used up, CPU can get stuck inside the while loop that looks for an available EPC page from remote nodes indefinitely, leading to a soft lockup. Note how nid_of_current will never be equal to nid in that while loop because nid_of_current is not set in sgx_numa_mask. Also worth mentioning is that it's perfectly fine for the firmware not to setup an EPC section on a node. While setting up an EPC section on each node can enhance performance, it is not a requirement for functionality. Rework the loop to start and end on a node that has SGX memory. This avoids the deadlock looking for the current SGX-lacking node to show up in the loop when it never will.(CVE-2024-49856)

In the Linux kernel, the following vulnerability has been resolved: mm, slub: avoid zeroing kmalloc redzone Since commit 946fa0dbf2d8 ("mm/slub: extend redzone check to extra allocated kmalloc space than requested"), setting orig_size treats the wasted space (object_size - orig_size) as a redzone. However with init_on_free=1 we clear the full object->size, including the redzone. Additionally we clear the object metadata, including the stored orig_size, making it zero, which makes check_object() treat the whole object as a redzone. These issues lead to the following BUG report with "slub_debug=FUZ init_on_free=1": [ 0.000000] ============================================================================= [ 0.000000] BUG kmalloc-8 (Not tainted): kmalloc Redzone overwritten [ 0.000000] ----------------------------------------------------------------------------- [ 0.000000] [ 0.000000] 0xffff000010032858-0xffff00001003285f @offset=2136. First byte 0x0 instead of 0xcc [ 0.000000] FIX kmalloc-8: Restoring kmalloc Redzone 0xffff000010032858-0xffff00001003285f=0xcc [ 0.000000] Slab 0xfffffdffc0400c80 objects=36 used=23 fp=0xffff000010032a18 flags=0x3fffe0000000200(workingset|node=0|zone=0|lastcpupid=0x1ffff) [ 0.000000] Object 0xffff000010032858 @offset=2136 fp=0xffff0000100328c8 [ 0.000000] [ 0.000000] Redzone ffff000010032850: cc cc cc cc cc cc cc cc ........ [ 0.000000] Object ffff000010032858: cc cc cc cc cc cc cc cc ........ [ 0.000000] Redzone ffff000010032860: cc cc cc cc cc cc cc cc ........ [ 0.000000] Padding ffff0000100328b4: 00 00 00 00 00 00 00 00 00 00 00 00 ............ [ 0.000000] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.11.0-rc3-next-20240814-00004-g61844c55c3f4 #144 [ 0.000000] Hardware name: NXP i.MX95 19X19 board (DT) [ 0.000000] Call trace: [ 0.000000] dump_backtrace+0x90/0xe8 [ 0.000000] show_stack+0x18/0x24 [ 0.000000] dump_stack_lvl+0x74/0x8c [ 0.000000] dump_stack+0x18/0x24 [ 0.000000] print_trailer+0x150/0x218 [ 0.000000] check_object+0xe4/0x454 [ 0.000000] free_to_partial_list+0x2f8/0x5ec To address the issue, use orig_size to clear the used area. And restore the value of orig_size after clear the remaining area. When CONFIG_SLUB_DEBUG not defined, (get_orig_size()' directly returns s->object_size. So when using memset to init the area, the size can simply be orig_size, as orig_size returns object_size when CONFIG_SLUB_DEBUG not enabled. And orig_size can never be bigger than object_size.(CVE-2024-49885)

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Initialize denominators' default to 1 [WHAT & HOW] Variables used as denominators and maybe not assigned to other values, should not be 0. Change their default to 1 so they are never 0. This fixes 10 DIVIDE_BY_ZERO issues reported by Coverity.(CVE-2024-49899)

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add null check for pipe_ctx->plane_state in dcn20_program_pipe This commit addresses a null pointer dereference issue in the dcn20_program_pipe function. The issue could occur when pipe_ctx->plane_state is null. The fix adds a check to ensure pipe_ctx->plane_state is not null before accessing. This prevents a null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn20/dcn20_hwseq.c:1925 dcn20_program_pipe() error: we previously assumed 'pipe_ctx->plane_state' could be null (see line 1877)(CVE-2024-49914)

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add NULL check for clk_mgr in dcn32_init_hw This commit addresses a potential null pointer dereference issue in the dcn32_init_hw function. The issue could occur when dc->clk_mgr is null. The fix adds a check to ensure dc->clk_mgr is not null before accessing its functions. This prevents a potential null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn32/dcn32_hwseq.c:961 dcn32_init_hw() error: we previously assumed 'dc->clk_mgr' could be null (see line 782)(CVE-2024-49915)

In the Linux kernel, the following vulnerability has been resolved: net: Fix an unsafe loop on the list The kernel may crash when deleting a genetlink family if there are still listeners for that family: Oops: Kernel access of bad area, sig: 11 [#1] ... NIP [c000000000c080bc] netlink_update_socket_mc+0x3c/0xc0 LR [c000000000c0f764] __netlink_clear_multicast_users+0x74/0xc0 Call Trace: __netlink_clear_multicast_users+0x74/0xc0 genl_unregister_family+0xd4/0x2d0 Change the unsafe loop on the list to a safe one, because inside the loop there is an element removal from this list.(CVE-2024-50024)

In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Stop the active perfmon before being destroyed When running kmscube with one or more performance monitors enabled via GALLIUM_HUD, the following kernel panic can occur: [ 55.008324] Unable to handle kernel paging request at virtual address 00000000052004a4 [ 55.008368] Mem abort info: [ 55.008377] ESR = 0x0000000096000005 [ 55.008387] EC = 0x25: DABT (current EL), IL = 32 bits [ 55.008402] SET = 0, FnV = 0 [ 55.008412] EA = 0, S1PTW = 0 [ 55.008421] FSC = 0x05: level 1 translation fault [ 55.008434] Data abort info: [ 55.008442] ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000 [ 55.008455] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 55.008467] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 55.008481] user pgtable: 4k pages, 39-bit VAs, pgdp=00000001046c6000 [ 55.008497] [00000000052004a4] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000 [ 55.008525] Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP [ 55.008542] Modules linked in: rfcomm [...] vc4 v3d snd_soc_hdmi_codec drm_display_helper gpu_sched drm_shmem_helper cec drm_dma_helper drm_kms_helper i2c_brcmstb drm drm_panel_orientation_quirks snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd backlight [ 55.008799] CPU: 2 PID: 166 Comm: v3d_bin Tainted: G C 6.6.47+rpt-rpi-v8 #1 Debian 1:6.6.47-1+rpt1 [ 55.008824] Hardware name: Raspberry Pi 4 Model B Rev 1.5 (DT) [ 55.008838] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 55.008855] pc : __mutex_lock.constprop.0+0x90/0x608 [ 55.008879] lr : __mutex_lock.constprop.0+0x58/0x608 [ 55.008895] sp : ffffffc080673cf0 [ 55.008904] x29: ffffffc080673cf0 x28: 0000000000000000 x27: ffffff8106188a28 [ 55.008926] x26: ffffff8101e78040 x25: ffffff8101baa6c0 x24: ffffffd9d989f148 [ 55.008947] x23: ffffffda1c2a4008 x22: 0000000000000002 x21: ffffffc080673d38 [ 55.008968] x20: ffffff8101238000 x19: ffffff8104f83188 x18: 0000000000000000 [ 55.008988] x17: 0000000000000000 x16: ffffffda1bd04d18 x15: 00000055bb08bc90 [ 55.009715] x14: 0000000000000000 x13: 0000000000000000 x12: ffffffda1bd4cbb0 [ 55.010433] x11: 00000000fa83b2da x10: 0000000000001a40 x9 : ffffffda1bd04d04 [ 55.011162] x8 : ffffff8102097b80 x7 : 0000000000000000 x6 : 00000000030a5857 [ 55.011880] x5 : 00ffffffffffffff x4 : 0300000005200470 x3 : 0300000005200470 [ 55.012598] x2 : ffffff8101238000 x1 : 0000000000000021 x0 : 0300000005200470 [ 55.013292] Call trace: [ 55.013959] __mutex_lock.constprop.0+0x90/0x608 [ 55.014646] __mutex_lock_slowpath+0x1c/0x30 [ 55.015317] mutex_lock+0x50/0x68 [ 55.015961] v3d_perfmon_stop+0x40/0xe0 [v3d] [ 55.016627] v3d_bin_job_run+0x10c/0x2d8 [v3d] [ 55.017282] drm_sched_main+0x178/0x3f8 [gpu_sched] [ 55.017921] kthread+0x11c/0x128 [ 55.018554] ret_from_fork+0x10/0x20 [ 55.019168] Code: f9400260 f1001c1f 54001ea9 927df000 (b9403401) [ 55.019776] ---[ end trace 0000000000000000 ]--- [ 55.020411] note: v3d_bin[166] exited with preempt_count 1 This issue arises because, upon closing the file descriptor (which happens when we interrupt kmscube), the active performance monitor is not stopped. Although all perfmons are destroyed in v3d_perfmon_close_file(), the active performance monitor's pointer (v3d->active_perfmon) is still retained. If kmscube is run again, the driver will attempt to stop the active performance monitor using the stale pointer in v3d->active_perfmon. However, this pointer is no longer valid because the previous process has already terminated, and all performance monitors associated with it have been destroyed and freed. To fix this, when the active performance monitor belongs to a given process, explicitly stop it before destroying and freeing it.(CVE-2024-50031)

In the Linux kernel, the following vulnerability has been resolved: netfilter: xtables: avoid NFPROTO_UNSPEC where needed syzbot managed to call xt_cluster match via ebtables: WARNING: CPU: 0 PID: 11 at net/netfilter/xt_cluster.c:72 xt_cluster_mt+0x196/0x780 [..] ebt_do_table+0x174b/0x2a40 Module registers to NFPROTO_UNSPEC, but it assumes ipv4/ipv6 packet processing. As this is only useful to restrict locally terminating TCP/UDP traffic, register this for ipv4 and ipv6 family only. Pablo points out that this is a general issue, direct users of the set/getsockopt interface can call into targets/matches that were only intended for use with ip(6)tables. Check all UNSPEC matches and targets for similar issues: - matches and targets are fine except if they assume skb_network_header() is valid -- this is only true when called from inet layer: ip(6) stack pulls the ip/ipv6 header into linear data area. - targets that return XT_CONTINUE or other xtables verdicts must be restricted too, they are incompatbile with the ebtables traverser, e.g. EBT_CONTINUE is a completely different value than XT_CONTINUE. Most matches/targets are changed to register for NFPROTO_IPV4/IPV6, as they are provided for use by ip(6)tables. The MARK target is also used by arptables, so register for NFPROTO_ARP too. While at it, bail out if connbytes fails to enable the corresponding conntrack family. This change passes the selftests in iptables.git.(CVE-2024-50038)

In the Linux kernel, the following vulnerability has been resolved: net/sched: accept TCA_STAB only for root qdisc Most qdiscs maintain their backlog using qdisc_pkt_len(skb) on the assumption it is invariant between the enqueue() and dequeue() handlers. Unfortunately syzbot can crash a host rather easily using a TBF + SFQ combination, with an STAB on SFQ [1] We can't support TCA_STAB on arbitrary level, this would require to maintain per-qdisc storage. [1] [ 88.796496] BUG: kernel NULL pointer dereference, address: 0000000000000000 [ 88.798611] #PF: supervisor read access in kernel mode [ 88.799014] #PF: error_code(0x0000) - not-present page [ 88.799506] PGD 0 P4D 0 [ 88.799829] Oops: Oops: 0000 [#1] SMP NOPTI [ 88.800569] CPU: 14 UID: 0 PID: 2053 Comm: b371744477 Not tainted 6.12.0-rc1-virtme #1117 [ 88.801107] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 88.801779] RIP: 0010:sfq_dequeue (net/sched/sch_sfq.c:272 net/sched/sch_sfq.c:499) sch_sfq [ 88.802544] Code: 0f b7 50 12 48 8d 04 d5 00 00 00 00 48 89 d6 48 29 d0 48 8b 91 c0 01 00 00 48 c1 e0 03 48 01 c2 66 83 7a 1a 00 7e c0 48 8b 3a <4c> 8b 07 4c 89 02 49 89 50 08 48 c7 47 08 00 00 00 00 48 c7 07 00 All code ======== 0: 0f b7 50 12 movzwl 0x12(%rax),%edx 4: 48 8d 04 d5 00 00 00 lea 0x0(,%rdx,8),%rax b: 00 c: 48 89 d6 mov %rdx,%rsi f: 48 29 d0 sub %rdx,%rax 12: 48 8b 91 c0 01 00 00 mov 0x1c0(%rcx),%rdx 19: 48 c1 e0 03 shl $0x3,%rax 1d: 48 01 c2 add %rax,%rdx 20: 66 83 7a 1a 00 cmpw $0x0,0x1a(%rdx) 25: 7e c0 jle 0xffffffffffffffe7 27: 48 8b 3a mov (%rdx),%rdi 2a:* 4c 8b 07 mov (%rdi),%r8 <-- trapping instruction 2d: 4c 89 02 mov %r8,(%rdx) 30: 49 89 50 08 mov %rdx,0x8(%r8) 34: 48 c7 47 08 00 00 00 movq $0x0,0x8(%rdi) 3b: 00 3c: 48 rex.W 3d: c7 .byte 0xc7 3e: 07 (bad) ... Code starting with the faulting instruction =========================================== 0: 4c 8b 07 mov (%rdi),%r8 3: 4c 89 02 mov %r8,(%rdx) 6: 49 89 50 08 mov %rdx,0x8(%r8) a: 48 c7 47 08 00 00 00 movq $0x0,0x8(%rdi) 11: 00 12: 48 rex.W 13: c7 .byte 0xc7 14: 07 (bad) ... [ 88.803721] RSP: 0018:ffff9a1f892b7d58 EFLAGS: 00000206 [ 88.804032] RAX: 0000000000000000 RBX: ffff9a1f8420c800 RCX: ffff9a1f8420c800 [ 88.804560] RDX: ffff9a1f81bc1440 RSI: 0000000000000000 RDI: 0000000000000000 [ 88.805056] RBP: ffffffffc04bb0e0 R08: 0000000000000001 R09: 00000000ff7f9a1f [ 88.805473] R10: 000000000001001b R11: 0000000000009a1f R12: 0000000000000140 [ 88.806194] R13: 0000000000000001 R14: ffff9a1f886df400 R15: ffff9a1f886df4ac [ 88.806734] FS: 00007f445601a740(0000) GS:ffff9a2e7fd80000(0000) knlGS:0000000000000000 [ 88.807225] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 88.807672] CR2: 0000000000000000 CR3: 000000050cc46000 CR4: 00000000000006f0 [ 88.808165] Call Trace: [ 88.808459] <TASK> [ 88.808710] ? __die (arch/x86/kernel/dumpstack.c:421 arch/x86/kernel/dumpstack.c:434) [ 88.809261] ? page_fault_oops (arch/x86/mm/fault.c:715) [ 88.809561] ? exc_page_fault (./arch/x86/include/asm/irqflags.h:26 ./arch/x86/include/asm/irqflags.h:87 ./arch/x86/include/asm/irqflags.h:147 arch/x86/mm/fault.c:1489 arch/x86/mm/fault.c:1539) [ 88.809806] ? asm_exc_page_fault (./arch/x86/include/asm/idtentry.h:623) [ 88.810074] ? sfq_dequeue (net/sched/sch_sfq.c:272 net/sched/sch_sfq.c:499) sch_sfq [ 88.810411] sfq_reset (net/sched/sch_sfq.c:525) sch_sfq [ 88.810671] qdisc_reset (./include/linux/skbuff.h:2135 ./include/linux/skbuff.h:2441 ./include/linux/skbuff.h:3304 ./include/linux/skbuff.h:3310 net/sched/sch_g ---truncated---(CVE-2024-50039)

In the Linux kernel, the following vulnerability has been resolved: netfilter: br_netfilter: fix panic with metadata_dst skb Fix a kernel panic in the br_netfilter module when sending untagged traffic via a VxLAN device. This happens during the check for fragmentation in br_nf_dev_queue_xmit. It is dependent on: 1) the br_netfilter module being loaded; 2) net.bridge.bridge-nf-call-iptables set to 1; 3) a bridge with a VxLAN (single-vxlan-device) netdevice as a bridge port; 4) untagged frames with size higher than the VxLAN MTU forwarded/flooded When forwarding the untagged packet to the VxLAN bridge port, before the netfilter hooks are called, br_handle_egress_vlan_tunnel is called and changes the skb_dst to the tunnel dst. The tunnel_dst is a metadata type of dst, i.e., skb_valid_dst(skb) is false, and metadata->dst.dev is NULL. Then in the br_netfilter hooks, in br_nf_dev_queue_xmit, there's a check for frames that needs to be fragmented: frames with higher MTU than the VxLAN device end up calling br_nf_ip_fragment, which in turns call ip_skb_dst_mtu. The ip_dst_mtu tries to use the skb_dst(skb) as if it was a valid dst with valid dst->dev, thus the crash. This case was never supported in the first place, so drop the packet instead. PING 10.0.0.2 (10.0.0.2) from 0.0.0.0 h1-eth0: 2000(2028) bytes of data. [ 176.291791] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000110 [ 176.292101] Mem abort info: [ 176.292184] ESR = 0x0000000096000004 [ 176.292322] EC = 0x25: DABT (current EL), IL = 32 bits [ 176.292530] SET = 0, FnV = 0 [ 176.292709] EA = 0, S1PTW = 0 [ 176.292862] FSC = 0x04: level 0 translation fault [ 176.293013] Data abort info: [ 176.293104] ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 [ 176.293488] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 176.293787] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 176.293995] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000043ef5000 [ 176.294166] [0000000000000110] pgd=0000000000000000, p4d=0000000000000000 [ 176.294827] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP [ 176.295252] Modules linked in: vxlan ip6_udp_tunnel udp_tunnel veth br_netfilter bridge stp llc ipv6 crct10dif_ce [ 176.295923] CPU: 0 PID: 188 Comm: ping Not tainted 6.8.0-rc3-g5b3fbd61b9d1 #2 [ 176.296314] Hardware name: linux,dummy-virt (DT) [ 176.296535] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 176.296808] pc : br_nf_dev_queue_xmit+0x390/0x4ec [br_netfilter] [ 176.297382] lr : br_nf_dev_queue_xmit+0x2ac/0x4ec [br_netfilter] [ 176.297636] sp : ffff800080003630 [ 176.297743] x29: ffff800080003630 x28: 0000000000000008 x27: ffff6828c49ad9f8 [ 176.298093] x26: ffff6828c49ad000 x25: 0000000000000000 x24: 00000000000003e8 [ 176.298430] x23: 0000000000000000 x22: ffff6828c4960b40 x21: ffff6828c3b16d28 [ 176.298652] x20: ffff6828c3167048 x19: ffff6828c3b16d00 x18: 0000000000000014 [ 176.298926] x17: ffffb0476322f000 x16: ffffb7e164023730 x15: 0000000095744632 [ 176.299296] x14: ffff6828c3f1c880 x13: 0000000000000002 x12: ffffb7e137926a70 [ 176.299574] x11: 0000000000000001 x10: ffff6828c3f1c898 x9 : 0000000000000000 [ 176.300049] x8 : ffff6828c49bf070 x7 : 0008460f18d5f20e x6 : f20e0100bebafeca [ 176.300302] x5 : ffff6828c7f918fe x4 : ffff6828c49bf070 x3 : 0000000000000000 [ 176.300586] x2 : 0000000000000000 x1 : ffff6828c3c7ad00 x0 : ffff6828c7f918f0 [ 176.300889] Call trace: [ 176.301123] br_nf_dev_queue_xmit+0x390/0x4ec [br_netfilter] [ 176.301411] br_nf_post_routing+0x2a8/0x3e4 [br_netfilter] [ 176.301703] nf_hook_slow+0x48/0x124 [ 176.302060] br_forward_finish+0xc8/0xe8 [bridge] [ 176.302371] br_nf_hook_thresh+0x124/0x134 [br_netfilter] [ 176.302605] br_nf_forward_finish+0x118/0x22c [br_netfilter] [ 176.302824] br_nf_forward_ip.part.0+0x264/0x290 [br_netfilter] [ 176.303136] br_nf_forward+0x2b8/0x4e0 [br_netfilter] [ 176.303359] nf_hook_slow+0x48/0x124 [ 176.303 ---truncated---(CVE-2024-50045)

In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-srv: Avoid null pointer deref during path establishment For RTRS path establishment, RTRS client initiates and completes con_num of connections. After establishing all its connections, the information is exchanged between the client and server through the info_req message. During this exchange, it is essential that all connections have been established, and the state of the RTRS srv path is CONNECTED. So add these sanity checks, to make sure we detect and abort process in error scenarios to avoid null pointer deref.(CVE-2024-50062)

In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: fix UaF read in mptcp_pm_nl_rm_addr_or_subflow Syzkaller reported this splat: ================================================================== BUG: KASAN: slab-use-after-free in mptcp_pm_nl_rm_addr_or_subflow+0xb44/0xcc0 net/mptcp/pm_netlink.c:881 Read of size 4 at addr ffff8880569ac858 by task syz.1.2799/14662 CPU: 0 UID: 0 PID: 14662 Comm: syz.1.2799 Not tainted 6.12.0-rc2-syzkaller-00307-g36c254515dc6 #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:377 [inline] print_report+0xc3/0x620 mm/kasan/report.c:488 kasan_report+0xd9/0x110 mm/kasan/report.c:601 mptcp_pm_nl_rm_addr_or_subflow+0xb44/0xcc0 net/mptcp/pm_netlink.c:881 mptcp_pm_nl_rm_subflow_received net/mptcp/pm_netlink.c:914 [inline] mptcp_nl_remove_id_zero_address+0x305/0x4a0 net/mptcp/pm_netlink.c:1572 mptcp_pm_nl_del_addr_doit+0x5c9/0x770 net/mptcp/pm_netlink.c:1603 genl_family_rcv_msg_doit+0x202/0x2f0 net/netlink/genetlink.c:1115 genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline] genl_rcv_msg+0x565/0x800 net/netlink/genetlink.c:1210 netlink_rcv_skb+0x165/0x410 net/netlink/af_netlink.c:2551 genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219 netlink_unicast_kernel net/netlink/af_netlink.c:1331 [inline] netlink_unicast+0x53c/0x7f0 net/netlink/af_netlink.c:1357 netlink_sendmsg+0x8b8/0xd70 net/netlink/af_netlink.c:1901 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg net/socket.c:744 [inline] _syssendmsg+0x9ae/0xb40 net/socket.c:2607 _sys_sendmsg+0x135/0x1e0 net/socket.c:2661 __sys_sendmsg+0x117/0x1f0 net/socket.c:2690 do_syscall_32_irqs_on arch/x86/entry/common.c:165 [inline] __do_fast_syscall_32+0x73/0x120 arch/x86/entry/common.c:386 do_fast_syscall_32+0x32/0x80 arch/x86/entry/common.c:411 entry_SYSENTER_compat_after_hwframe+0x84/0x8e RIP: 0023:0xf7fe4579 Code: b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 00 00 00 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00 RSP: 002b:00000000f574556c EFLAGS: 00000296 ORIG_RAX: 0000000000000172 RAX: ffffffffffffffda RBX: 000000000000000b RCX: 0000000020000140 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000296 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK> Allocated by task 5387: kasan_save_stack+0x33/0x60 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:377 [inline] __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:394 kmalloc_noprof include/linux/slab.h:878 [inline] kzalloc_noprof include/linux/slab.h:1014 [inline] subflow_create_ctx+0x87/0x2a0 net/mptcp/subflow.c:1803 subflow_ulp_init+0xc3/0x4d0 net/mptcp/subflow.c:1956 __tcp_set_ulp net/ipv4/tcp_ulp.c:146 [inline] tcp_set_ulp+0x326/0x7f0 net/ipv4/tcp_ulp.c:167 mptcp_subflow_create_socket+0x4ae/0x10a0 net/mptcp/subflow.c:1764 __mptcp_subflow_connect+0x3cc/0x1490 net/mptcp/subflow.c:1592 mptcp_pm_create_subflow_or_signal_addr+0xbda/0x23a0 net/mptcp/pm_netlink.c:642 mptcp_pm_nl_fully_established net/mptcp/pm_netlink.c:650 [inline] mptcp_pm_nl_work+0x3a1/0x4f0 net/mptcp/pm_netlink.c:943 mptcp_worker+0x15a/0x1240 net/mptcp/protocol.c:2777 process_one_work+0x958/0x1b30 kernel/workqueue.c:3229 process_scheduled_works kernel/workqueue.c:3310 [inline] worker_thread+0x6c8/0xf00 kernel/workqueue.c:3391 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/ke ---truncated---(CVE-2024-50085)

In the Linux kernel, the following vulnerability has been resolved: thermal: intel: int340x: processor: Fix warning during module unload The processor_thermal driver uses pcim_device_enable() to enable a PCI device, which means the device will be automatically disabled on driver detach. Thus there is no need to call pci_disable_device() again on it. With recent PCI device resource management improvements, e.g. commit f748a07a0b64 ("PCI: Remove legacy pcim_release()"), this problem is exposed and triggers the warining below. [ 224.010735] proc_thermal_pci 0000:00:04.0: disabling already-disabled device [ 224.010747] WARNING: CPU: 8 PID: 4442 at drivers/pci/pci.c:2250 pci_disable_device+0xe5/0x100 ... [ 224.010844] Call Trace: [ 224.010845] <TASK> [ 224.010847] ? show_regs+0x6d/0x80 [ 224.010851] ? __warn+0x8c/0x140 [ 224.010854] ? pci_disable_device+0xe5/0x100 [ 224.010856] ? report_bug+0x1c9/0x1e0 [ 224.010859] ? handle_bug+0x46/0x80 [ 224.010862] ? exc_invalid_op+0x1d/0x80 [ 224.010863] ? asm_exc_invalid_op+0x1f/0x30 [ 224.010867] ? pci_disable_device+0xe5/0x100 [ 224.010869] ? pci_disable_device+0xe5/0x100 [ 224.010871] ? kfree+0x21a/0x2b0 [ 224.010873] pcim_disable_device+0x20/0x30 [ 224.010875] devm_action_release+0x16/0x20 [ 224.010878] release_nodes+0x47/0xc0 [ 224.010880] devres_release_all+0x9f/0xe0 [ 224.010883] device_unbind_cleanup+0x12/0x80 [ 224.010885] device_release_driver_internal+0x1ca/0x210 [ 224.010887] driver_detach+0x4e/0xa0 [ 224.010889] bus_remove_driver+0x6f/0xf0 [ 224.010890] driver_unregister+0x35/0x60 [ 224.010892] pci_unregister_driver+0x44/0x90 [ 224.010894] proc_thermal_pci_driver_exit+0x14/0x5f0 [processor_thermal_device_pci] ... [ 224.010921] ---[ end trace 0000000000000000 ]--- Remove the excess pci_disable_device() calls. rjw: Subject and changelog edits

In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Set SDEV_OFFLINE when UFS is shut down There is a history of deadlock if reboot is performed at the beginning of booting. SDEV_QUIESCE was set for all LU's scsi_devices by UFS shutdown, and at that time the audio driver was waiting on blk_mq_submit_bio() holding a mutex_lock while reading the fw binary. After that, a deadlock issue occurred while audio driver shutdown was waiting for mutex_unlock of blk_mq_submit_bio(). To solve this, set SDEV_OFFLINE for all LUs except WLUN, so that any I/O that comes down after a UFS shutdown will return an error. [ 31.907781]I[0: swapper/0: 0] 1 130705007 1651079834 11289729804 0 D( 2) 3 ffffff882e208000 * init [device_shutdown] [ 31.907793]I[0: swapper/0: 0] Mutex: 0xffffff8849a2b8b0: owner[0xffffff882e28cb00 kworker/6:0 :49] [ 31.907806]I[0: swapper/0: 0] Call trace: [ 31.907810]I[0: swapper/0: 0] __switch_to+0x174/0x338 [ 31.907819]I[0: swapper/0: 0] __schedule+0x5ec/0x9cc [ 31.907826]I[0: swapper/0: 0] schedule+0x7c/0xe8 [ 31.907834]I[0: swapper/0: 0] schedule_preempt_disabled+0x24/0x40 [ 31.907842]I[0: swapper/0: 0] __mutex_lock+0x408/0xdac [ 31.907849]I[0: swapper/0: 0] __mutex_lock_slowpath+0x14/0x24 [ 31.907858]I[0: swapper/0: 0] mutex_lock+0x40/0xec [ 31.907866]I[0: swapper/0: 0] device_shutdown+0x108/0x280 [ 31.907875]I[0: swapper/0: 0] kernel_restart+0x4c/0x11c [ 31.907883]I[0: swapper/0: 0] __arm64_sys_reboot+0x15c/0x280 [ 31.907890]I[0: swapper/0: 0] invoke_syscall+0x70/0x158 [ 31.907899]I[0: swapper/0: 0] el0_svc_common+0xb4/0xf4 [ 31.907909]I[0: swapper/0: 0] do_el0_svc+0x2c/0xb0 [ 31.907918]I[0: swapper/0: 0] el0_svc+0x34/0xe0 [ 31.907928]I[0: swapper/0: 0] el0t_64_sync_handler+0x68/0xb4 [ 31.907937]I[0: swapper/0: 0] el0t_64_sync+0x1a0/0x1a4 [ 31.908774]I[0: swapper/0: 0] 49 0 11960702 11236868007 0 D( 2) 6 ffffff882e28cb00 * kworker/6:0 [__bio_queue_enter] [ 31.908783]I[0: swapper/0: 0] Call trace: [ 31.908788]I[0: swapper/0: 0] __switch_to+0x174/0x338 [ 31.908796]I[0: swapper/0: 0] __schedule+0x5ec/0x9cc [ 31.908803]I[0: swapper/0: 0] schedule+0x7c/0xe8 [ 31.908811]I[0: swapper/0: 0] __bio_queue_enter+0xb8/0x178 [ 31.908818]I[0: swapper/0: 0] blk_mq_submit_bio+0x194/0x67c [ 31.908827]I[0: swapper/0: 0] __submit_bio+0xb8/0x19c(CVE-2024-50098)

In the Linux kernel, the following vulnerability has been resolved: ACPI: PRM: Find EFI_MEMORY_RUNTIME block for PRM handler and context PRMT needs to find the correct type of block to translate the PA-VA mapping for EFI runtime services. The issue arises because the PRMT is finding a block of type EFI_CONVENTIONAL_MEMORY, which is not appropriate for runtime services as described in Section 2.2.2 (Runtime Services) of the UEFI Specification [1]. Since the PRM handler is a type of runtime service, this causes an exception when the PRM handler is called. [Firmware Bug]: Unable to handle paging request in EFI runtime service WARNING: CPU: 22 PID: 4330 at drivers/firmware/efi/runtime-wrappers.c:341 __efi_queue_work+0x11c/0x170 Call trace: Let PRMT find a block with EFI_MEMORY_RUNTIME for PRM handler and PRM context. If no suitable block is found, a warning message will be printed, but the procedure continues to manage the next PRM handler. However, if the PRM handler is actually called without proper allocation, it would result in a failure during error handling. By using the correct memory types for runtime services, ensure that the PRM handler and the context are properly mapped in the virtual address space during runtime, preventing the paging request error. The issue is really that only memory that has been remapped for runtime by the firmware can be used by the PRM handler, and so the region needs to have the EFI_MEMORY_RUNTIME attribute. rjw: Subject and changelog edits

In the Linux kernel, the following vulnerability has been resolved: udf: fix uninit-value use in udf_get_fileshortad Check for overflow when computing alen in udf_current_aext to mitigate later uninit-value use in udf_get_fileshortad KMSAN bug[1]. After applying the patch reproducer did not trigger any issue[2]. [1] https://syzkaller.appspot.com/bug?extid=8901c4560b7ab5c2f9df [2] https://syzkaller.appspot.com/x/log.txt?x=10242227980000(CVE-2024-50143)

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: bnep: fix wild-memory-access in proto_unregister There's issue as follows: KASAN: maybe wild-memory-access in range [0xdead...108-0xdead...10f] CPU: 3 UID: 0 PID: 2805 Comm: rmmod Tainted: G W RIP: 0010:proto_unregister+0xee/0x400 Call Trace: <TASK> __do_sys_delete_module+0x318/0x580 do_syscall_64+0xc1/0x1d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f As bnep_init() ignore bnep_sock_init()'s return value, and bnep_sock_init() will cleanup all resource. Then when remove bnep module will call bnep_sock_cleanup() to cleanup sock's resource. To solve above issue just return bnep_sock_init()'s return value in bnep_exit().(CVE-2024-50148)

In the Linux kernel, the following vulnerability has been resolved: tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). Martin KaFai Lau reported use-after-free [0] in reqsk_timer_handler(). """ We are seeing a use-after-free from a bpf prog attached to trace_tcp_retransmit_synack. The program passes the req->sk to the bpf_sk_storage_get_tracing kernel helper which does check for null before using it. """ The commit 83fccfc3940c ("inet: fix potential deadlock in reqsk_queue_unlink()") added timer_pending() in reqsk_queue_unlink() not to call del_timer_sync() from reqsk_timer_handler(), but it introduced a small race window. Before the timer is called, expire_timers() calls detach_timer(timer, true) to clear timer->entry.pprev and marks it as not pending. If reqsk_queue_unlink() checks timer_pending() just after expire_timers() calls detach_timer(), TCP will miss del_timer_sync(); the reqsk timer will continue running and send multiple SYN+ACKs until it expires. The reported UAF could happen if req->sk is close()d earlier than the timer expiration, which is 63s by default. The scenario would be 1. inet_csk_complete_hashdance() calls inet_csk_reqsk_queue_drop(), but del_timer_sync() is missed 2. reqsk timer is executed and scheduled again 3. req->sk is accept()ed and reqsk_put() decrements rsk_refcnt, but reqsk timer still has another one, and inet_csk_accept() does not clear req->sk for non-TFO sockets 4. sk is close()d 5. reqsk timer is executed again, and BPF touches req->sk Let's not use timer_pending() by passing the caller context to __inet_csk_reqsk_queue_drop(). Note that reqsk timer is pinned, so the issue does not happen in most use cases. [1] [0] BUG: KFENCE: use-after-free read in bpf_sk_storage_get_tracing+0x2e/0x1b0 Use-after-free read at 0x00000000a891fb3a (in kfence-#1): bpf_sk_storage_get_tracing+0x2e/0x1b0 bpf_prog_5ea3e95db6da0438_tcp_retransmit_synack+0x1d20/0x1dda bpf_trace_run2+0x4c/0xc0 tcp_rtx_synack+0xf9/0x100 reqsk_timer_handler+0xda/0x3d0 run_timer_softirq+0x292/0x8a0 irq_exit_rcu+0xf5/0x320 sysvec_apic_timer_interrupt+0x6d/0x80 asm_sysvec_apic_timer_interrupt+0x16/0x20 intel_idle_irq+0x5a/0xa0 cpuidle_enter_state+0x94/0x273 cpu_startup_entry+0x15e/0x260 start_secondary+0x8a/0x90 secondary_startup_64_no_verify+0xfa/0xfb kfence-#1: 0x00000000a72cc7b6-0x00000000d97616d9, size=2376, cache=TCPv6 allocated by task 0 on cpu 9 at 260507.901592s: sk_prot_alloc+0x35/0x140 sk_clone_lock+0x1f/0x3f0 inet_csk_clone_lock+0x15/0x160 tcp_create_openreq_child+0x1f/0x410 tcp_v6_syn_recv_sock+0x1da/0x700 tcp_check_req+0x1fb/0x510 tcp_v6_rcv+0x98b/0x1420 ipv6_list_rcv+0x2258/0x26e0 napi_complete_done+0x5b1/0x2990 mlx5e_napi_poll+0x2ae/0x8d0 net_rx_action+0x13e/0x590 irq_exit_rcu+0xf5/0x320 common_interrupt+0x80/0x90 asm_common_interrupt+0x22/0x40 cpuidle_enter_state+0xfb/0x273 cpu_startup_entry+0x15e/0x260 start_secondary+0x8a/0x90 secondary_startup_64_no_verify+0xfa/0xfb freed by task 0 on cpu 9 at 260507.927527s: rcu_core_si+0x4ff/0xf10 irq_exit_rcu+0xf5/0x320 sysvec_apic_timer_interrupt+0x6d/0x80 asm_sysvec_apic_timer_interrupt+0x16/0x20 cpuidle_enter_state+0xfb/0x273 cpu_startup_entry+0x15e/0x260 start_secondary+0x8a/0x90 secondary_startup_64_no_verify+0xfa/0xfb(CVE-2024-50154)

In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Avoid CPU lockups due fifo occupancy check loop Driver waits indefinitely for the fifo occupancy to go below a threshold as soon as the pacing interrupt is received. This can cause soft lockup on one of the processors, if the rate of DB is very high. Add a loop count for FPGA and exit the __wait_for_fifo_occupancy_below_th if the loop is taking more time. Pacing will be continuing until the occupancy is below the threshold. This is ensured by the checks in bnxt_re_pacing_timer_exp and further scheduling the work for pacing based on the fifo occupancy.(CVE-2024-50157)

In the Linux kernel, the following vulnerability has been resolved: bpf: devmap: provide rxq after redirect rxq contains a pointer to the device from where the redirect happened. Currently, the BPF program that was executed after a redirect via BPF_MAP_TYPE_DEVMAP does not have it set. This is particularly bad since accessing ingress_ifindex, e.g. SEC("xdp") int prog(struct xdp_md pkt) { return bpf_redirect_map(&dev_redirect_map, 0, 0); } SEC("xdp/devmap") int prog_after_redirect(struct xdp_md *pkt) { bpf_printk("ifindex %i", pkt->ingress_ifindex); return XDP_PASS; } depends on access to rxq, so a NULL pointer gets dereferenced: <1>[ 574.475170] BUG: kernel NULL pointer dereference, address: 0000000000000000 <1>[ 574.475188] #PF: supervisor read access in kernel mode <1>[ 574.475194] #PF: error_code(0x0000) - not-present page <6>[ 574.475199] PGD 0 P4D 0 <4>[ 574.475207] Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI <4>[ 574.475217] CPU: 4 UID: 0 PID: 217 Comm: kworker/4:1 Not tainted 6.11.0-rc5-reduced-00859-g780801200300 #23 <4>[ 574.475226] Hardware name: Intel(R) Client Systems NUC13ANHi7/NUC13ANBi7, BIOS ANRPL357.0026.2023.0314.1458 03/14/2023 <4>[ 574.475231] Workqueue: mld mld_ifc_work <4>[ 574.475247] RIP: 0010:bpf_prog_5e13354d9cf5018a_prog_after_redirect+0x17/0x3c <4>[ 574.475257] Code: cc cc cc cc cc cc cc 80 00 00 00 cc cc cc cc cc cc cc cc f3 0f 1e fa 0f 1f 44 00 00 66 90 55 48 89 e5 f3 0f 1e fa 48 8b 57 20 <48> 8b 52 00 8b 92 e0 00 00 00 48 bf f8 a6 d5 c4 5d a0 ff ff be 0b <4>[ 574.475263] RSP: 0018:ffffa62440280c98 EFLAGS: 00010206 <4>[ 574.475269] RAX: ffffa62440280cd8 RBX: 0000000000000001 RCX: 0000000000000000 <4>[ 574.475274] RDX: 0000000000000000 RSI: ffffa62440549048 RDI: ffffa62440280ce0 <4>[ 574.475278] RBP: ffffa62440280c98 R08: 0000000000000002 R09: 0000000000000001 <4>[ 574.475281] R10: ffffa05dc8b98000 R11: ffffa05f577fca40 R12: ffffa05dcab24000 <4>[ 574.475285] R13: ffffa62440280ce0 R14: ffffa62440549048 R15: ffffa62440549000 <4>[ 574.475289] FS: 0000000000000000(0000) GS:ffffa05f4f700000(0000) knlGS:0000000000000000 <4>[ 574.475294] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4>[ 574.475298] CR2: 0000000000000000 CR3: 000000025522e000 CR4: 0000000000f50ef0 <4>[ 574.475303] PKRU: 55555554 <4>[ 574.475306] Call Trace: <4>[ 574.475313] <IRQ> <4>[ 574.475318] ? __die+0x23/0x70 <4>[ 574.475329] ? page_fault_oops+0x180/0x4c0 <4>[ 574.475339] ? skb_pp_cow_data+0x34c/0x490 <4>[ 574.475346] ? kmem_cache_free+0x257/0x280 <4>[ 574.475357] ? exc_page_fault+0x67/0x150 <4>[ 574.475368] ? asm_exc_page_fault+0x26/0x30 <4>[ 574.475381] ? bpf_prog_5e13354d9cf5018a_prog_after_redirect+0x17/0x3c <4>[ 574.475386] bq_xmit_all+0x158/0x420 <4>[ 574.475397] __dev_flush+0x30/0x90 <4>[ 574.475407] veth_poll+0x216/0x250 [veth] <4>[ 574.475421] __napi_poll+0x28/0x1c0 <4>[ 574.475430] net_rx_action+0x32d/0x3a0 <4>[ 574.475441] handle_softirqs+0xcb/0x2c0 <4>[ 574.475451] do_softirq+0x40/0x60 <4>[ 574.475458] </IRQ> <4>[ 574.475461] <TASK> <4>[ 574.475464] __local_bh_enable_ip+0x66/0x70 <4>[ 574.475471] __dev_queue_xmit+0x268/0xe40 <4>[ 574.475480] ? selinux_ip_postroute+0x213/0x420 <4>[ 574.475491] ? alloc_skb_with_frags+0x4a/0x1d0 <4>[ 574.475502] ip6_finish_output2+0x2be/0x640 <4>[ 574.475512] ? nf_hook_slow+0x42/0xf0 <4>[ 574.475521] ip6_finish_output+0x194/0x300 <4>[ 574.475529] ? __pfx_ip6_finish_output+0x10/0x10 <4>[ 574.475538] mld_sendpack+0x17c/0x240 <4>[ 574.475548] mld_ifc_work+0x192/0x410 <4>[ 574.475557] process_one_work+0x15d/0x380 <4>[ 574.475566] worker_thread+0x29d/0x3a0 <4>[ 574.475573] ? __pfx_worker_thread+0x10/0x10 <4>[ 574.475580] ? __pfx_worker_thread+0x10/0x10 <4>[ 574.475587] kthread+0xcd/0x100 <4>[ 574.475597] ? __pfx_kthread+0x10/0x10 <4>[ 574.475606] ret_from_fork+0x31/0x50 <4>[ 574.475615] ? __pfx_kthread+0x10/0x10 <4>[ 574.475623] ret_from_fork_asm+0x1a/0x ---truncated---(CVE-2024-50162)

In the Linux kernel, the following vulnerability has been resolved: fsl/fman: Fix refcount handling of fman-related devices In mac_probe() there are multiple calls to of_find_device_by_node(), fman_bind() and fman_port_bind() which takes references to of_dev->dev. Not all references taken by these calls are released later on error path in mac_probe() and in mac_remove() which lead to reference leaks. Add references release.(CVE-2024-50166)

In the Linux kernel, the following vulnerability has been resolved: vsock: Update rx_bytes on read_skb() Make sure virtio_transport_inc_rx_pkt() and virtio_transport_dec_rx_pkt() calls are balanced (i.e. virtio_vsock_sock::rx_bytes doesn't lie) after vsock_transport::read_skb(). While here, also inform the peer that we've freed up space and it has more credit. Failing to update rx_bytes after packet is dequeued leads to a warning on SOCK_STREAM recv(): [ 233.396654] rx_queue is empty, but rx_bytes is non-zero [ 233.396702] WARNING: CPU: 11 PID: 40601 at net/vmw_vsock/virtio_transport_common.c:589(CVE-2024-50169)

In the Linux kernel, the following vulnerability has been resolved: net: bcmasp: fix potential memory leak in bcmasp_xmit() The bcmasp_xmit() returns NETDEV_TX_OK without freeing skb in case of mapping fails, add dev_kfree_skb() to fix it.(CVE-2024-50170)

In the Linux kernel, the following vulnerability has been resolved: net: systemport: fix potential memory leak in bcm_sysport_xmit() The bcm_sysport_xmit() returns NETDEV_TX_OK without freeing skb in case of dma_map_single() fails, add dev_kfree_skb() to fix it.(CVE-2024-50171)

In the Linux kernel, the following vulnerability has been resolved: secretmem: disable memfd_secret() if arch cannot set direct map Return -ENOSYS from memfd_secret() syscall if !can_set_direct_map(). This is the case for example on some arm64 configurations, where marking 4k PTEs in the direct map not present can only be done if the direct map is set up at 4k granularity in the first place (as ARM's break-before-make semantics do not easily allow breaking apart large/gigantic pages). More precisely, on arm64 systems with !can_set_direct_map(), set_direct_map_invalid_noflush() is a no-op, however it returns success (0) instead of an error. This means that memfd_secret will seemingly "work" (e.g. syscall succeeds, you can mmap the fd and fault in pages), but it does not actually achieve its goal of removing its memory from the direct map. Note that with this patch, memfd_secret() will start erroring on systems where can_set_direct_map() returns false (arm64 with CONFIG_RODATA_FULL_DEFAULT_ENABLED=n, CONFIG_DEBUG_PAGEALLOC=n and CONFIG_KFENCE=n), but that still seems better than the current silent failure. Since CONFIG_RODATA_FULL_DEFAULT_ENABLED defaults to 'y', most arm64 systems actually have a working memfd_secret() and aren't be affected. From going through the iterations of the original memfd_secret patch series, it seems that disabling the syscall in these scenarios was the intended behavior [1] (preferred over having set_direct_map_invalid_noflush return an error as that would result in SIGBUSes at page-fault time), however the check for it got dropped between v16 [2] and v17 [3], when secretmem moved away from CMA allocations. [1]: https://lore.kernel.org/lkml/20201124164930.GK8537@kernel.org/ [2]: https://lore.kernel.org/lkml/20210121122723.3446-11-rppt@kernel.org/#t [3]: https://lore.kernel.org/lkml/20201125092208.12544-10-rppt@kernel.org/(CVE-2024-50182)

In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v4: Don't allow a VMOVP on a dying VPE Kunkun Jiang reported that there is a small window of opportunity for userspace to force a change of affinity for a VPE while the VPE has already been unmapped, but the corresponding doorbell interrupt still visible in /proc/irq/. Plug the race by checking the value of vmapp_count, which tracks whether the VPE is mapped ot not, and returning an error in this case. This involves making vmapp_count common to both GICv4.1 and its v4.0 ancestor.(CVE-2024-50192)

In the Linux kernel, the following vulnerability has been resolved: posix-clock: Fix missing timespec64 check in pc_clock_settime() As Andrew pointed out, it will make sense that the PTP core checked timespec64 struct's tv_sec and tv_nsec range before calling ptp->info->settime64(). As the man manual of clock_settime() said, if tp.tv_sec is negative or tp.tv_nsec is outside the range [0..999,999,999], it should return EINVAL, which include dynamic clocks which handles PTP clock, and the condition is consistent with timespec64_valid(). As Thomas suggested, timespec64_valid() only check the timespec is valid, but not ensure that the time is in a valid range, so check it ahead using timespec64_valid_strict() in pc_clock_settime() and return -EINVAL if not valid. There are some drivers that use tp->tv_sec and tp->tv_nsec directly to write registers without validity checks and assume that the higher layer has checked it, which is dangerous and will benefit from this, such as hclge_ptp_settime(), igb_ptp_settime_i210(), _rcar_gen4_ptp_settime(), and some drivers can remove the checks of itself.(CVE-2024-50195)

In the Linux kernel, the following vulnerability has been resolved: bpf, arm64: Fix address emission with tag-based KASAN enabled When BPF_TRAMP_F_CALL_ORIG is enabled, the address of a bpf_tramp_image struct on the stack is passed during the size calculation pass and an address on the heap is passed during code generation. This may cause a heap buffer overflow if the heap address is tagged because emit_a64_mov_i64() will emit longer code than it did during the size calculation pass. The same problem could occur without tag-based KASAN if one of the 16-bit words of the stack address happened to be all-ones during the size calculation pass. Fix the problem by assuming the worst case (4 instructions) when calculating the size of the bpf_tramp_image address emission.(CVE-2024-50203)

In the Linux kernel, the following vulnerability has been resolved: ALSA: firewire-lib: Avoid division by zero in apply_constraint_to_size() The step variable is initialized to zero. It is changed in the loop, but if it's not changed it will remain zero. Add a variable check before the division. The observed behavior was introduced by commit 826b5de90c0b ("ALSA: firewire-lib: fix insufficient PCM rule for period/buffer size"), and it is difficult to show that any of the interval parameters will satisfy the snd_interval_test() condition with data from the amdtp_rate_table[] table. Found by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-50205)

In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Fix a bug while setting up Level-2 PBL pages Avoid memory corruption while setting up Level-2 PBL pages for the non MR resources when num_pages > 256K. There will be a single PDE page address (contiguous pages in the case of > PAGE_SIZE), but, current logic assumes multiple pages, leading to invalid memory access after 256K PBL entries in the PDE.(CVE-2024-50208)

In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Add a check for memory allocation __alloc_pbl() can return error when memory allocation fails. Driver is not checking the status on one of the instances.(CVE-2024-50209)

In the Linux kernel, the following vulnerability has been resolved: xfs: fix finding a last resort AG in xfs_filestream_pick_ag When the main loop in xfs_filestream_pick_ag fails to find a suitable AG it tries to just pick the online AG. But the loop for that uses args->pag as loop iterator while the later code expects pag to be set. Fix this by reusing the max_pag case for this last resort, and also add a check for impossible case of no AG just to make sure that the uninitialized pag doesn't even escape in theory.(CVE-2024-50216)

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix use-after-free of block device file in __btrfs_free_extra_devids() Mounting btrfs from two images (which have the same one fsid and two different dev_uuids) in certain executing order may trigger an UAF for variable 'device->bdev_file' in __btrfs_free_extra_devids(). And following are the details: 1. Attach image_1 to loop0, attach image_2 to loop1, and scan btrfs devices by ioctl(BTRFS_IOC_SCAN_DEV): / btrfs_device_1 → loop0 fs_device \ btrfs_device_2 → loop1 2. mount /dev/loop0 /mnt btrfs_open_devices btrfs_device_1->bdev_file = btrfs_get_bdev_and_sb(loop0) btrfs_device_2->bdev_file = btrfs_get_bdev_and_sb(loop1) btrfs_fill_super open_ctree fail: btrfs_close_devices // -ENOMEM btrfs_close_bdev(btrfs_device_1) fput(btrfs_device_1->bdev_file) // btrfs_device_1->bdev_file is freed btrfs_close_bdev(btrfs_device_2) fput(btrfs_device_2->bdev_file) 3. mount /dev/loop1 /mnt btrfs_open_devices btrfs_get_bdev_and_sb(&bdev_file) // EIO, btrfs_device_1->bdev_file is not assigned, // which points to a freed memory area btrfs_device_2->bdev_file = btrfs_get_bdev_and_sb(loop1) btrfs_fill_super open_ctree btrfs_free_extra_devids if (btrfs_device_1->bdev_file) fput(btrfs_device_1->bdev_file) // UAF ! Fix it by setting 'device->bdev_file' as 'NULL' after closing the btrfs_device in btrfs_close_one_device().(CVE-2024-50217)

In the Linux kernel, the following vulnerability has been resolved: sched/numa: Fix the potential null pointer dereference in task_numa_work() When running stress-ng-vm-segv test, we found a null pointer dereference error in task_numa_work(). Here is the backtrace: [323676.066985] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000020 ...... [323676.067108] CPU: 35 PID: 2694524 Comm: stress-ng-vm-se ...... [323676.067113] pstate: 23401009 (nzCv daif +PAN -UAO +TCO +DIT +SSBS BTYPE=--) [323676.067115] pc : vma_migratable+0x1c/0xd0 [323676.067122] lr : task_numa_work+0x1ec/0x4e0 [323676.067127] sp : ffff8000ada73d20 [323676.067128] x29: ffff8000ada73d20 x28: 0000000000000000 x27: 000000003e89f010 [323676.067130] x26: 0000000000080000 x25: ffff800081b5c0d8 x24: ffff800081b27000 [323676.067133] x23: 0000000000010000 x22: 0000000104d18cc0 x21: ffff0009f7158000 [323676.067135] x20: 0000000000000000 x19: 0000000000000000 x18: ffff8000ada73db8 [323676.067138] x17: 0001400000000000 x16: ffff800080df40b0 x15: 0000000000000035 [323676.067140] x14: ffff8000ada73cc8 x13: 1fffe0017cc72001 x12: ffff8000ada73cc8 [323676.067142] x11: ffff80008001160c x10: ffff000be639000c x9 : ffff8000800f4ba4 [323676.067145] x8 : ffff000810375000 x7 : ffff8000ada73974 x6 : 0000000000000001 [323676.067147] x5 : 0068000b33e26707 x4 : 0000000000000001 x3 : ffff0009f7158000 [323676.067149] x2 : 0000000000000041 x1 : 0000000000004400 x0 : 0000000000000000 [323676.067152] Call trace: [323676.067153] vma_migratable+0x1c/0xd0 [323676.067155] task_numa_work+0x1ec/0x4e0 [323676.067157] task_work_run+0x78/0xd8 [323676.067161] do_notify_resume+0x1ec/0x290 [323676.067163] el0_svc+0x150/0x160 [323676.067167] el0t_64_sync_handler+0xf8/0x128 [323676.067170] el0t_64_sync+0x17c/0x180 [323676.067173] Code: d2888001 910003fd f9000bf3 aa0003f3 (f9401000) [323676.067177] SMP: stopping secondary CPUs [323676.070184] Starting crashdump kernel... stress-ng-vm-segv in stress-ng is used to stress test the SIGSEGV error handling function of the system, which tries to cause a SIGSEGV error on return from unmapping the whole address space of the child process. Normally this program will not cause kernel crashes. But before the munmap system call returns to user mode, a potential task_numa_work() for numa balancing could be added and executed. In this scenario, since the child process has no vma after munmap, the vma_next() in task_numa_work() will return a null pointer even if the vma iterator restarts from 0. Recheck the vma pointer before dereferencing it in task_numa_work().(CVE-2024-50223)

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix kernel bug due to missing clearing of checked flag Syzbot reported that in directory operations after nilfs2 detects filesystem corruption and degrades to read-only, __block_write_begin_int(), which is called to prepare block writes, may fail the BUG_ON check for accesses exceeding the folio/page size, triggering a kernel bug. This was found to be because the "checked" flag of a page/folio was not cleared when it was discarded by nilfs2's own routine, which causes the sanity check of directory entries to be skipped when the directory page/folio is reloaded. So, fix that. This was necessary when the use of nilfs2's own page discard routine was applied to more than just metadata files.(CVE-2024-50230)

In the Linux kernel, the following vulnerability has been resolved: wifi: iwlegacy: Clear stale interrupts before resuming device iwl4965 fails upon resume from hibernation on my laptop. The reason seems to be a stale interrupt which isn't being cleared out before interrupts are enabled. We end up with a race beween the resume trying to bring things back up, and the restart work (queued form the interrupt handler) trying to bring things down. Eventually the whole thing blows up. Fix the problem by clearing out any stale interrupts before interrupts get enabled during resume. Here's a debug log of the indicent: [ 12.042589] ieee80211 phy0: il_isr ISR inta 0x00000080, enabled 0xaa00008b, fh 0x00000000 [ 12.042625] ieee80211 phy0: il4965_irq_tasklet inta 0x00000080, enabled 0x00000000, fh 0x00000000 [ 12.042651] iwl4965 0000:10:00.0: RF_KILL bit toggled to enable radio. [ 12.042653] iwl4965 0000:10:00.0: On demand firmware reload [ 12.042690] ieee80211 phy0: il4965_irq_tasklet End inta 0x00000000, enabled 0xaa00008b, fh 0x00000000, flags 0x00000282 [ 12.052207] ieee80211 phy0: il4965_mac_start enter [ 12.052212] ieee80211 phy0: il_prep_station Add STA to driver ID 31: ff:ff:ff:ff:ff:ff [ 12.052244] ieee80211 phy0: il4965_set_hw_ready hardware ready [ 12.052324] ieee80211 phy0: il_apm_init Init card's basic functions [ 12.052348] ieee80211 phy0: il_apm_init L1 Enabled; Disabling L0S [ 12.055727] ieee80211 phy0: il4965_load_bsm Begin load bsm [ 12.056140] ieee80211 phy0: il4965_verify_bsm Begin verify bsm [ 12.058642] ieee80211 phy0: il4965_verify_bsm BSM bootstrap uCode image OK [ 12.058721] ieee80211 phy0: il4965_load_bsm BSM write complete, poll 1 iterations [ 12.058734] ieee80211 phy0: __il4965_up iwl4965 is coming up [ 12.058737] ieee80211 phy0: il4965_mac_start Start UP work done. [ 12.058757] ieee80211 phy0: __il4965_down iwl4965 is going down [ 12.058761] ieee80211 phy0: il_scan_cancel_timeout Scan cancel timeout [ 12.058762] ieee80211 phy0: il_do_scan_abort Not performing scan to abort [ 12.058765] ieee80211 phy0: il_clear_ucode_stations Clearing ucode stations in driver [ 12.058767] ieee80211 phy0: il_clear_ucode_stations No active stations found to be cleared [ 12.058819] ieee80211 phy0: _il_apm_stop Stop card, put in low power state [ 12.058827] ieee80211 phy0: _il_apm_stop_master stop master [ 12.058864] ieee80211 phy0: il4965_clear_free_frames 0 frames on pre-allocated heap on clear. [ 12.058869] ieee80211 phy0: Hardware restart was requested [ 16.132299] iwl4965 0000:10:00.0: START_ALIVE timeout after 4000ms. [ 16.132303] ------------[ cut here ]------------ [ 16.132304] Hardware became unavailable upon resume. This could be a software issue prior to suspend or a hardware issue. [ 16.132338] WARNING: CPU: 0 PID: 181 at net/mac80211/util.c:1826 ieee80211_reconfig+0x8f/0x14b0 [mac80211] [ 16.132390] Modules linked in: ctr ccm sch_fq_codel xt_tcpudp xt_multiport xt_state iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv4 ip_tables x_tables binfmt_misc joydev mousedev btusb btrtl btintel btbcm bluetooth ecdh_generic ecc iTCO_wdt i2c_dev iwl4965 iwlegacy coretemp snd_hda_codec_analog pcspkr psmouse mac80211 snd_hda_codec_generic libarc4 sdhci_pci cqhci sha256_generic sdhci libsha256 firewire_ohci snd_hda_intel snd_intel_dspcfg mmc_core snd_hda_codec snd_hwdep firewire_core led_class iosf_mbi snd_hda_core uhci_hcd lpc_ich crc_itu_t cfg80211 ehci_pci ehci_hcd snd_pcm usbcore mfd_core rfkill snd_timer snd usb_common soundcore video parport_pc parport intel_agp wmi intel_gtt backlight e1000e agpgart evdev [ 16.132456] CPU: 0 UID: 0 PID: 181 Comm: kworker/u8:6 Not tainted 6.11.0-cl+ #143 [ 16.132460] Hardware name: Hewlett-Packard HP Compaq 6910p/30BE, BIOS 68MCU Ver. F.19 07/06/2010 [ 16.132463] Workqueue: async async_run_entry_fn [ 16.132469] RIP: 0010:ieee80211_reconfig+0x8f/0x14b0 [mac80211] [ 16.132501] Code: da 02 00 0 ---truncated---(CVE-2024-50234)

In the Linux kernel, the following vulnerability has been resolved: wifi: ath10k: Fix memory leak in management tx In the current logic, memory is allocated for storing the MSDU context during management packet TX but this memory is not being freed during management TX completion. Similar leaks are seen in the management TX cleanup logic. Kmemleak reports this problem as below, unreferenced object 0xffffff80b64ed250 (size 16): comm "kworker/u16:7", pid 148, jiffies 4294687130 (age 714.199s) hex dump (first 16 bytes): 00 2b d8 d8 80 ff ff ff c4 74 e9 fd 07 00 00 00 .+.......t...... backtrace: [<ffffffe6e7b245dc>] __kmem_cache_alloc_node+0x1e4/0x2d8 [<ffffffe6e7adde88>] kmalloc_trace+0x48/0x110 [<ffffffe6bbd765fc>] ath10k_wmi_tlv_op_gen_mgmt_tx_send+0xd4/0x1d8 [ath10k_core] [<ffffffe6bbd3eed4>] ath10k_mgmt_over_wmi_tx_work+0x134/0x298 [ath10k_core] [<ffffffe6e78d5974>] process_scheduled_works+0x1ac/0x400 [<ffffffe6e78d60b8>] worker_thread+0x208/0x328 [<ffffffe6e78dc890>] kthread+0x100/0x1c0 [<ffffffe6e78166c0>] ret_from_fork+0x10/0x20 Free the memory during completion and cleanup to fix the leak. Protect the mgmt_pending_tx idr_remove() operation in ath10k_wmi_tlv_op_cleanup_mgmt_tx_send() using ar->data_lock similar to other instances. Tested-on: WCN3990 hw1.0 SNOC WLAN.HL.2.0-01387-QCAHLSWMTPLZ-1(CVE-2024-50236)

In the Linux kernel, the following vulnerability has been resolved: NFSD: Initialize struct nfsd4_copy earlier Ensure the refcount and async_copies fields are initialized early. cleanup_async_copy() will reference these fields if an error occurs in nfsd4_copy(). If they are not correctly initialized, at the very least, a refcount underflow occurs.(CVE-2024-50241)

In the Linux kernel, the following vulnerability has been resolved: ntfs3: Add bounds checking to mi_enum_attr() Added bounds checking to make sure that every attr don't stray beyond valid memory region.(CVE-2024-50248)

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci: fix null-ptr-deref in hci_read_supported_codecs Fix __hci_cmd_sync_sk() to return not NULL for unknown opcodes. __hci_cmd_sync_sk() returns NULL if a command returns a status event. However, it also returns NULL where an opcode doesn't exist in the hci_cc table because hci_cmd_complete_evt() assumes status = skb->data[0] for unknown opcodes. This leads to null-ptr-deref in cmd_sync for HCI_OP_READ_LOCAL_CODECS as there is no hci_cc for HCI_OP_READ_LOCAL_CODECS, which always assumes status = skb->data[0]. KASAN: null-ptr-deref in range [0x0000000000000070-0x0000000000000077] CPU: 1 PID: 2000 Comm: kworker/u9:5 Not tainted 6.9.0-ga6bcb805883c-dirty #10 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Workqueue: hci7 hci_power_on RIP: 0010:hci_read_supported_codecs+0xb9/0x870 net/bluetooth/hci_codec.c:138 Code: 08 48 89 ef e8 b8 c1 8f fd 48 8b 75 00 e9 96 00 00 00 49 89 c6 48 ba 00 00 00 00 00 fc ff df 4c 8d 60 70 4c 89 e3 48 c1 eb 03 <0f> b6 04 13 84 c0 0f 85 82 06 00 00 41 83 3c 24 02 77 0a e8 bf 78 RSP: 0018:ffff888120bafac8 EFLAGS: 00010212 RAX: 0000000000000000 RBX: 000000000000000e RCX: ffff8881173f0040 RDX: dffffc0000000000 RSI: ffffffffa58496c0 RDI: ffff88810b9ad1e4 RBP: ffff88810b9ac000 R08: ffffffffa77882a7 R09: 1ffffffff4ef1054 R10: dffffc0000000000 R11: fffffbfff4ef1055 R12: 0000000000000070 R13: 0000000000000000 R14: 0000000000000000 R15: ffff88810b9ac000 FS: 0000000000000000(0000) GS:ffff8881f6c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f6ddaa3439e CR3: 0000000139764003 CR4: 0000000000770ef0 PKRU: 55555554 Call Trace: <TASK> hci_read_local_codecs_sync net/bluetooth/hci_sync.c:4546 [inline] hci_init_stage_sync net/bluetooth/hci_sync.c:3441 [inline] hci_init4_sync net/bluetooth/hci_sync.c:4706 [inline] hci_init_sync net/bluetooth/hci_sync.c:4742 [inline] hci_dev_init_sync net/bluetooth/hci_sync.c:4912 [inline] hci_dev_open_sync+0x19a9/0x2d30 net/bluetooth/hci_sync.c:4994 hci_dev_do_open net/bluetooth/hci_core.c:483 [inline] hci_power_on+0x11e/0x560 net/bluetooth/hci_core.c:1015 process_one_work kernel/workqueue.c:3267 [inline] process_scheduled_works+0x8ef/0x14f0 kernel/workqueue.c:3348 worker_thread+0x91f/0xe50 kernel/workqueue.c:3429 kthread+0x2cb/0x360 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-50255)

In the Linux kernel, the following vulnerability has been resolved: net: fix crash when config small gso_max_size/gso_ipv4_max_size Config a small gso_max_size/gso_ipv4_max_size will lead to an underflow in sk_dst_gso_max_size(), which may trigger a BUG_ON crash, because sk->sk_gso_max_size would be much bigger than device limits. Call Trace: tcp_write_xmit tso_segs = tcp_init_tso_segs(skb, mss_now); tcp_set_skb_tso_segs tcp_skb_pcount_set // skb->len = 524288, mss_now = 8 // u16 tso_segs = 524288/8 = 65535 -> 0 tso_segs = DIV_ROUND_UP(skb->len, mss_now) BUG_ON(!tso_segs) Add check for the minimum value of gso_max_size and gso_ipv4_max_size.(CVE-2024-50258)

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix out-of-bounds write in trie_get_next_key() trie_get_next_key() allocates a node stack with size trie->max_prefixlen, while it writes (trie->max_prefixlen + 1) nodes to the stack when it has full paths from the root to leaves. For example, consider a trie with max_prefixlen is 8, and the nodes with key 0x00/0, 0x00/1, 0x00/2, ... 0x00/8 inserted. Subsequent calls to trie_get_next_key with _key with .prefixlen = 8 make 9 nodes be written on the node stack with size 8.(CVE-2024-50262)

In the Linux kernel, the following vulnerability has been resolved: ocfs2: remove entry once instead of null-ptr-dereference in ocfs2_xa_remove() Syzkaller is able to provoke null-ptr-dereference in ocfs2_xa_remove(): [ 57.319872] (a.out,1161,7):ocfs2_xa_remove:2028 ERROR: status = -12 [ 57.320420] (a.out,1161,7):ocfs2_xa_cleanup_value_truncate:1999 ERROR: Partial truncate while removing xattr overlay.upper. Leaking 1 clusters and removing the entry [ 57.321727] BUG: kernel NULL pointer dereference, address: 0000000000000004 [...] [ 57.325727] RIP: 0010:ocfs2_xa_block_wipe_namevalue+0x2a/0xc0 [...] [ 57.331328] Call Trace: [ 57.331477] <TASK> [...] [ 57.333511] ? do_user_addr_fault+0x3e5/0x740 [ 57.333778] ? exc_page_fault+0x70/0x170 [ 57.334016] ? asm_exc_page_fault+0x2b/0x30 [ 57.334263] ? __pfx_ocfs2_xa_block_wipe_namevalue+0x10/0x10 [ 57.334596] ? ocfs2_xa_block_wipe_namevalue+0x2a/0xc0 [ 57.334913] ocfs2_xa_remove_entry+0x23/0xc0 [ 57.335164] ocfs2_xa_set+0x704/0xcf0 [ 57.335381] ? _raw_spin_unlock+0x1a/0x40 [ 57.335620] ? ocfs2_inode_cache_unlock+0x16/0x20 [ 57.335915] ? trace_preempt_on+0x1e/0x70 [ 57.336153] ? start_this_handle+0x16c/0x500 [ 57.336410] ? preempt_count_sub+0x50/0x80 [ 57.336656] ? _raw_read_unlock+0x20/0x40 [ 57.336906] ? start_this_handle+0x16c/0x500 [ 57.337162] ocfs2_xattr_block_set+0xa6/0x1e0 [ 57.337424] __ocfs2_xattr_set_handle+0x1fd/0x5d0 [ 57.337706] ? ocfs2_start_trans+0x13d/0x290 [ 57.337971] ocfs2_xattr_set+0xb13/0xfb0 [ 57.338207] ? dput+0x46/0x1c0 [ 57.338393] ocfs2_xattr_trusted_set+0x28/0x30 [ 57.338665] ? ocfs2_xattr_trusted_set+0x28/0x30 [ 57.338948] __vfs_removexattr+0x92/0xc0 [ 57.339182] __vfs_removexattr_locked+0xd5/0x190 [ 57.339456] ? preempt_count_sub+0x50/0x80 [ 57.339705] vfs_removexattr+0x5f/0x100 [...] Reproducer uses faultinject facility to fail ocfs2_xa_remove() -> ocfs2_xa_value_truncate() with -ENOMEM. In this case the comment mentions that we can return 0 if ocfs2_xa_cleanup_value_truncate() is going to wipe the entry anyway. But the following 'rc' check is wrong and execution flow do 'ocfs2_xa_remove_entry(loc);' twice: * 1st: in ocfs2_xa_cleanup_value_truncate(); * 2nd: returning back to ocfs2_xa_remove() instead of going to 'out'. Fix this by skipping the 2nd removal of the same entry and making syzkaller repro happy.(CVE-2024-50265)

In the Linux kernel, the following vulnerability has been resolved: usb: musb: sunxi: Fix accessing an released usb phy Commit 6ed05c68cbca ("usb: musb: sunxi: Explicitly release USB PHY on exit") will cause that usb phy @glue->xceiv is accessed after released. 1) register platform driver @sunxi_musb_driver // get the usb phy @glue->xceiv sunxi_musb_probe() -> devm_usb_get_phy(). 2) register and unregister platform driver @musb_driver musb_probe() -> sunxi_musb_init() use the phy here //the phy is released here musb_remove() -> sunxi_musb_exit() -> devm_usb_put_phy() 3) register @musb_driver again musb_probe() -> sunxi_musb_init() use the phy here but the phy has been released at 2). ... Fixed by reverting the commit, namely, removing devm_usb_put_phy() from sunxi_musb_exit().(CVE-2024-50269)

In the Linux kernel, the following vulnerability has been resolved: signal: restore the override_rlimit logic Prior to commit d64696905554 ("Reimplement RLIMIT_SIGPENDING on top of ucounts") UCOUNT_RLIMIT_SIGPENDING rlimit was not enforced for a class of signals. However now it's enforced unconditionally, even if override_rlimit is set. This behavior change caused production issues. For example, if the limit is reached and a process receives a SIGSEGV signal, sigqueue_alloc fails to allocate the necessary resources for the signal delivery, preventing the signal from being delivered with siginfo. This prevents the process from correctly identifying the fault address and handling the error. From the user-space perspective, applications are unaware that the limit has been reached and that the siginfo is effectively 'corrupted'. This can lead to unpredictable behavior and crashes, as we observed with java applications. Fix this by passing override_rlimit into inc_rlimit_get_ucounts() and skip the comparison to max there if override_rlimit is set. This effectively restores the old behavior.(CVE-2024-50271)

In the Linux kernel, the following vulnerability has been resolved: filemap: Fix bounds checking in filemap_read() If the caller supplies an iocb->ki_pos value that is close to the filesystem upper limit, and an iterator with a count that causes us to overflow that limit, then filemap_read() enters an infinite loop. This behaviour was discovered when testing xfstests generic/525 with the "localio" optimisation for loopback NFS mounts.(CVE-2024-50272)

In the Linux kernel, the following vulnerability has been resolved: btrfs: reinitialize delayed ref list after deleting it from the list At insert_delayed_ref() if we need to update the action of an existing ref to BTRFS_DROP_DELAYED_REF, we delete the ref from its ref head's ref_add_list using list_del(), which leaves the ref's add_list member not reinitialized, as list_del() sets the next and prev members of the list to LIST_POISON1 and LIST_POISON2, respectively. If later we end up calling drop_delayed_ref() against the ref, which can happen during merging or when destroying delayed refs due to a transaction abort, we can trigger a crash since at drop_delayed_ref() we call list_empty() against the ref's add_list, which returns false since the list was not reinitialized after the list_del() and as a consequence we call list_del() again at drop_delayed_ref(). This results in an invalid list access since the next and prev members are set to poison pointers, resulting in a splat if CONFIG_LIST_HARDENED and CONFIG_DEBUG_LIST are set or invalid poison pointer dereferences otherwise. So fix this by deleting from the list with list_del_init() instead.(CVE-2024-50273)

In the Linux kernel, the following vulnerability has been resolved: arm64/sve: Discard stale CPU state when handling SVE traps The logic for handling SVE traps manipulates saved FPSIMD/SVE state incorrectly, and a race with preemption can result in a task having TIF_SVE set and TIF_FOREIGN_FPSTATE clear even though the live CPU state is stale (e.g. with SVE traps enabled). This has been observed to result in warnings from do_sve_acc() where SVE traps are not expected while TIF_SVE is set: | if (test_and_set_thread_flag(TIF_SVE)) | WARN_ON(1); / SVE access shouldn't have trapped / Warnings of this form have been reported intermittently, e.g. https://lore.kernel.org/linux-arm-kernel/CA+G9fYtEGe_DhY2Ms7+L7NKsLYUomGsgqpdBj+QwDLeSg=JhGg@mail.gmail.com/ https://lore.kernel.org/linux-arm-kernel/000000000000511e9a060ce5a45c@google.com/ The race can occur when the SVE trap handler is preempted before and after manipulating the saved FPSIMD/SVE state, starting and ending on the same CPU, e.g. | void do_sve_acc(unsigned long esr, struct pt_regs regs) | { | // Trap on CPU 0 with TIF_SVE clear, SVE traps enabled | // task->fpsimd_cpu is 0. | // per_cpu_ptr(&fpsimd_last_state, 0) is task. | | ... | | // Preempted; migrated from CPU 0 to CPU 1. | // TIF_FOREIGN_FPSTATE is set. | | get_cpu_fpsimd_context(); | | if (test_and_set_thread_flag(TIF_SVE)) | WARN_ON(1); / SVE access shouldn't have trapped */ | | sve_init_regs() { | if (!test_thread_flag(TIF_FOREIGN_FPSTATE)) { | ... | } else { | fpsimd_to_sve(current); | current->thread.fp_type = FP_STATE_SVE; | } | } | | put_cpu_fpsimd_context(); | | // Preempted; migrated from CPU 1 to CPU 0. | // task->fpsimd_cpu is still 0 | // If per_cpu_ptr(&fpsimd_last_state, 0) is still task then: | // - Stale HW state is reused (with SVE traps enabled) | // - TIF_FOREIGN_FPSTATE is cleared | // - A return to userspace skips HW state restore | } Fix the case where the state is not live and TIF_FOREIGN_FPSTATE is set by calling fpsimd_flush_task_state() to detach from the saved CPU state. This ensures that a subsequent context switch will not reuse the stale CPU state, and will instead set TIF_FOREIGN_FPSTATE, forcing the new state to be reloaded from memory prior to a return to userspace.(CVE-2024-50275)

In the Linux kernel, the following vulnerability has been resolved: net: vertexcom: mse102x: Fix possible double free of TX skb The scope of the TX skb is wider than just mse102x_tx_frame_spi(), so in case the TX skb room needs to be expanded, we should free the the temporary skb instead of the original skb. Otherwise the original TX skb pointer would be freed again in mse102x_tx_work(), which leads to crashes: Internal error: Oops: 0000000096000004 [#2] PREEMPT SMP CPU: 0 PID: 712 Comm: kworker/0:1 Tainted: G D 6.6.23 Hardware name: chargebyte Charge SOM DC-ONE (DT) Workqueue: events mse102x_tx_work [mse102x] pstate: 20400009 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : skb_release_data+0xb8/0x1d8 lr : skb_release_data+0x1ac/0x1d8 sp : ffff8000819a3cc0 x29: ffff8000819a3cc0 x28: ffff0000046daa60 x27: ffff0000057f2dc0 x26: ffff000005386c00 x25: 0000000000000002 x24: 00000000ffffffff x23: 0000000000000000 x22: 0000000000000001 x21: ffff0000057f2e50 x20: 0000000000000006 x19: 0000000000000000 x18: ffff00003fdacfcc x17: e69ad452d0c49def x16: 84a005feff870102 x15: 0000000000000000 x14: 000000000000024a x13: 0000000000000002 x12: 0000000000000000 x11: 0000000000000400 x10: 0000000000000930 x9 : ffff00003fd913e8 x8 : fffffc00001bc008 x7 : 0000000000000000 x6 : 0000000000000008 x5 : ffff00003fd91340 x4 : 0000000000000000 x3 : 0000000000000009 x2 : 00000000fffffffe x1 : 0000000000000000 x0 : 0000000000000000 Call trace: skb_release_data+0xb8/0x1d8 kfree_skb_reason+0x48/0xb0 mse102x_tx_work+0x164/0x35c [mse102x] process_one_work+0x138/0x260 worker_thread+0x32c/0x438 kthread+0x118/0x11c ret_from_fork+0x10/0x20 Code: aa1303e0 97fffab6 72001c1f 54000141 (f9400660)(CVE-2024-50276)

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix slab-use-after-free in smb3_preauth_hash_rsp ksmbd_user_session_put should be called under smb3_preauth_hash_rsp(). It will avoid freeing session before calling smb3_preauth_hash_rsp().(CVE-2024-50283)

In the Linux kernel, the following vulnerability has been resolved: ksmbd: Fix the missing xa_store error check xa_store() can fail, it return xa_err(-EINVAL) if the entry cannot be stored in an XArray, or xa_err(-ENOMEM) if memory allocation failed, so check error for xa_store() to fix it.(CVE-2024-50284)

In the Linux kernel, the following vulnerability has been resolved: media: av7110: fix a spectre vulnerability As warned by smatch: drivers/staging/media/av7110/av7110_ca.c:270 dvb_ca_ioctl() warn: potential spectre issue 'av7110->ci_slot' [w] (local cap) There is a spectre-related vulnerability at the code. Fix it.(CVE-2024-50289)

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix missing locking causing hanging calls If a call gets aborted (e.g. because kafs saw a signal) between it being queued for connection and the I/O thread picking up the call, the abort will be prioritised over the connection and it will be removed from local->new_client_calls by rxrpc_disconnect_client_call() without a lock being held. This may cause other calls on the list to disappear if a race occurs. Fix this by taking the client_call_lock when removing a call from whatever list its ->wait_link happens to be on.(CVE-2024-50294)

In the Linux kernel, the following vulnerability has been resolved: net: enetc: allocate vf_state during PF probes In the previous implementation, vf_state is allocated memory only when VF is enabled. However, net_device_ops::ndo_set_vf_mac() may be called before VF is enabled to configure the MAC address of VF. If this is the case, enetc_pf_set_vf_mac() will access vf_state, resulting in access to a null pointer. The simplified error log is as follows. root@ls1028ardb:~# ip link set eno0 vf 1 mac 00:0c:e7:66:77:89 [ 173.543315] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000004 [ 173.637254] pc : enetc_pf_set_vf_mac+0x3c/0x80 Message from sy [ 173.641973] lr : do_setlink+0x4a8/0xec8 [ 173.732292] Call trace: [ 173.734740] enetc_pf_set_vf_mac+0x3c/0x80 [ 173.738847] __rtnl_newlink+0x530/0x89c [ 173.742692] rtnl_newlink+0x50/0x7c [ 173.746189] rtnetlink_rcv_msg+0x128/0x390 [ 173.750298] netlink_rcv_skb+0x60/0x130 [ 173.754145] rtnetlink_rcv+0x18/0x24 [ 173.757731] netlink_unicast+0x318/0x380 [ 173.761665] netlink_sendmsg+0x17c/0x3c8(CVE-2024-50298)

In the Linux kernel, the following vulnerability has been resolved: sctp: properly validate chunk size in sctp_sf_ootb() A size validation fix similar to that in Commit 50619dbf8db7 ("sctp: add size validation when walking chunks") is also required in sctp_sf_ootb() to address a crash reported by syzbot: BUG: KMSAN: uninit-value in sctp_sf_ootb+0x7f5/0xce0 net/sctp/sm_statefuns.c:3712 sctp_sf_ootb+0x7f5/0xce0 net/sctp/sm_statefuns.c:3712 sctp_do_sm+0x181/0x93d0 net/sctp/sm_sideeffect.c:1166 sctp_endpoint_bh_rcv+0xc38/0xf90 net/sctp/endpointola.c:407 sctp_inq_push+0x2ef/0x380 net/sctp/inqueue.c:88 sctp_rcv+0x3831/0x3b20 net/sctp/input.c:243 sctp4_rcv+0x42/0x50 net/sctp/protocol.c:1159 ip_protocol_deliver_rcu+0xb51/0x13d0 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x336/0x500 net/ipv4/ip_input.c:233(CVE-2024-50299)

In the Linux kernel, the following vulnerability has been resolved: mctp i2c: handle NULL header address daddr can be NULL if there is no neighbour table entry present, in that case the tx packet should be dropped. saddr will usually be set by MCTP core, but check for NULL in case a packet is transmitted by a different protocol.(CVE-2024-53043)

In the Linux kernel, the following vulnerability has been resolved: arm64: dts: imx8ulp: correct the flexspi compatible string The flexspi on imx8ulp only has 16 LUTs, and imx8mm flexspi has 32 LUTs, so correct the compatible string here, otherwise will meet below error: [ 1.119072] ------------[ cut here ]------------ [ 1.123926] WARNING: CPU: 0 PID: 1 at drivers/spi/spi-nxp-fspi.c:855 nxp_fspi_exec_op+0xb04/0xb64 [ 1.133239] Modules linked in: [ 1.136448] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.11.0-rc6-next-20240902-00001-g131bf9439dd9 #69 [ 1.146821] Hardware name: NXP i.MX8ULP EVK (DT) [ 1.151647] pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 1.158931] pc : nxp_fspi_exec_op+0xb04/0xb64 [ 1.163496] lr : nxp_fspi_exec_op+0xa34/0xb64 [ 1.168060] sp : ffff80008002b2a0 [ 1.171526] x29: ffff80008002b2d0 x28: 0000000000000000 x27: 0000000000000000 [ 1.179002] x26: ffff2eb645542580 x25: ffff800080610014 x24: ffff800080610000 [ 1.186480] x23: ffff2eb645548080 x22: 0000000000000006 x21: ffff2eb6455425e0 [ 1.193956] x20: 0000000000000000 x19: ffff80008002b5e0 x18: ffffffffffffffff [ 1.201432] x17: ffff2eb644467508 x16: 0000000000000138 x15: 0000000000000002 [ 1.208907] x14: 0000000000000000 x13: ffff2eb6400d8080 x12: 00000000ffffff00 [ 1.216378] x11: 0000000000000000 x10: ffff2eb6400d8080 x9 : ffff2eb697adca80 [ 1.223850] x8 : ffff2eb697ad3cc0 x7 : 0000000100000000 x6 : 0000000000000001 [ 1.231324] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 00000000000007a6 [ 1.238795] x2 : 0000000000000000 x1 : 00000000000001ce x0 : 00000000ffffff92 [ 1.246267] Call trace: [ 1.248824] nxp_fspi_exec_op+0xb04/0xb64 [ 1.253031] spi_mem_exec_op+0x3a0/0x430 [ 1.257139] spi_nor_read_id+0x80/0xcc [ 1.261065] spi_nor_scan+0x1ec/0xf10 [ 1.264901] spi_nor_probe+0x108/0x2fc [ 1.268828] spi_mem_probe+0x6c/0xbc [ 1.272574] spi_probe+0x84/0xe4 [ 1.275958] really_probe+0xbc/0x29c [ 1.279713] __driver_probe_device+0x78/0x12c [ 1.284277] driver_probe_device+0xd8/0x15c [ 1.288660] __device_attach_driver+0xb8/0x134 [ 1.293316] bus_for_each_drv+0x88/0xe8 [ 1.297337] __device_attach+0xa0/0x190 [ 1.301353] device_initial_probe+0x14/0x20 [ 1.305734] bus_probe_device+0xac/0xb0 [ 1.309752] device_add+0x5d0/0x790 [ 1.313408] __spi_add_device+0x134/0x204 [ 1.317606] of_register_spi_device+0x3b4/0x590 [ 1.322348] spi_register_controller+0x47c/0x754 [ 1.327181] devm_spi_register_controller+0x4c/0xa4 [ 1.332289] nxp_fspi_probe+0x1cc/0x2b0 [ 1.336307] platform_probe+0x68/0xc4 [ 1.340145] really_probe+0xbc/0x29c [ 1.343893] __driver_probe_device+0x78/0x12c [ 1.348457] driver_probe_device+0xd8/0x15c [ 1.352838] __driver_attach+0x90/0x19c [ 1.356857] bus_for_each_dev+0x7c/0xdc [ 1.360877] driver_attach+0x24/0x30 [ 1.364624] bus_add_driver+0xe4/0x208 [ 1.368552] driver_register+0x5c/0x124 [ 1.372573] __platform_driver_register+0x28/0x34 [ 1.377497] nxp_fspi_driver_init+0x1c/0x28 [ 1.381888] do_one_initcall+0x80/0x1c8 [ 1.385908] kernel_init_freeable+0x1c4/0x28c [ 1.390472] kernel_init+0x20/0x1d8 [ 1.394138] ret_from_fork+0x10/0x20 [ 1.397885] ---[ end trace 0000000000000000 ]--- [ 1.407908] ------------[ cut here ]------------(CVE-2024-53046)

In the Linux kernel, the following vulnerability has been resolved: mptcp: init: protect sched with rcu_read_lock Enabling CONFIG_PROVE_RCU_LIST with its dependence CONFIG_RCU_EXPERT creates this splat when an MPTCP socket is created: ============================= WARNING: suspicious RCU usage 6.12.0-rc2+ #11 Not tainted ----------------------------- net/mptcp/sched.c:44 RCU-list traversed in non-reader section!! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 no locks held by mptcp_connect/176. stack backtrace: CPU: 0 UID: 0 PID: 176 Comm: mptcp_connect Not tainted 6.12.0-rc2+ #11 Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:123) lockdep_rcu_suspicious (kernel/locking/lockdep.c:6822) mptcp_sched_find (net/mptcp/sched.c:44 (discriminator 7)) mptcp_init_sock (net/mptcp/protocol.c:2867 (discriminator 1)) ? sock_init_data_uid (arch/x86/include/asm/atomic.h:28) inet_create.part.0.constprop.0 (net/ipv4/af_inet.c:386) ? __sock_create (include/linux/rcupdate.h:347 (discriminator 1)) __sock_create (net/socket.c:1576) __sys_socket (net/socket.c:1671) ? __pfxsyssocket (net/socket.c:1712) ? do_user_addr_fault (arch/x86/mm/fault.c:1419 (discriminator 1)) x64_sys_socket (net/socket.c:1728) do_syscall_64 (arch/x86/entry/common.c:52 (discriminator 1)) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) That's because when the socket is initialised, rcu_read_lock() is not used despite the explicit comment written above the declaration of mptcp_sched_find() in sched.c. Adding the missing lock/unlock avoids the warning.(CVE-2024-53047)

In the Linux kernel, the following vulnerability has been resolved: io_uring/rw: fix missing NOWAIT check for O_DIRECT start write When io_uring starts a write, it'll call kiocb_start_write() to bump the super block rwsem, preventing any freezes from happening while that write is in-flight. The freeze side will grab that rwsem for writing, excluding any new writers from happening and waiting for existing writes to finish. But io_uring unconditionally uses kiocb_start_write(), which will block if someone is currently attempting to freeze the mount point. This causes a deadlock where freeze is waiting for previous writes to complete, but the previous writes cannot complete, as the task that is supposed to complete them is blocked waiting on starting a new write. This results in the following stuck trace showing that dependency with the write blocked starting a new write: task:fio state:D stack:0 pid:886 tgid:886 ppid:876 Call trace: __switch_to+0x1d8/0x348 __schedule+0x8e8/0x2248 schedule+0x110/0x3f0 percpu_rwsem_wait+0x1e8/0x3f8 __percpu_down_read+0xe8/0x500 io_write+0xbb8/0xff8 io_issue_sqe+0x10c/0x1020 io_submit_sqes+0x614/0x2110 __arm64_sys_io_uring_enter+0x524/0x1038 invoke_syscall+0x74/0x268 el0_svc_common.constprop.0+0x160/0x238 do_el0_svc+0x44/0x60 el0_svc+0x44/0xb0 el0t_64_sync_handler+0x118/0x128 el0t_64_sync+0x168/0x170 INFO: task fsfreeze:7364 blocked for more than 15 seconds. Not tainted 6.12.0-rc5-00063-g76aaf945701c #7963 with the attempting freezer stuck trying to grab the rwsem: task:fsfreeze state:D stack:0 pid:7364 tgid:7364 ppid:995 Call trace: __switch_to+0x1d8/0x348 __schedule+0x8e8/0x2248 schedule+0x110/0x3f0 percpu_down_write+0x2b0/0x680 freeze_super+0x248/0x8a8 do_vfs_ioctl+0x149c/0x1b18 __arm64_sys_ioctl+0xd0/0x1a0 invoke_syscall+0x74/0x268 el0_svc_common.constprop.0+0x160/0x238 do_el0_svc+0x44/0x60 el0_svc+0x44/0xb0 el0t_64_sync_handler+0x118/0x128 el0t_64_sync+0x168/0x170 Fix this by having the io_uring side honor IOCB_NOWAIT, and only attempt a blocking grab of the super block rwsem if it isn't set. For normal issue where IOCB_NOWAIT would always be set, this returns -EAGAIN which will have io_uring core issue a blocking attempt of the write. That will in turn also get completions run, ensuring forward progress. Since freezing requires CAP_SYS_ADMIN in the first place, this isn't something that can be triggered by a regular user.(CVE-2024-53052)

In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: fix 6 GHz scan construction If more than 255 colocated APs exist for the set of all APs found during 2.4/5 GHz scanning, then the 6 GHz scan construction will loop forever since the loop variable has type u8, which can never reach the number found when that's bigger than 255, and is stored in a u32 variable. Also move it into the loops to have a smaller scope. Using a u32 there is fine, we limit the number of APs in the scan list and each has a limit on the number of RNR entries due to the frame size. With a limit of 1000 scan results, a frame size upper bound of 4096 (really it's more like ~2300) and a TBTT entry size of at least 11, we get an upper bound for the number of ~372k, well in the bounds of a u32.(CVE-2024-53055)

In the Linux kernel, the following vulnerability has been resolved: media: s5p-jpeg: prevent buffer overflows The current logic allows word to be less than 2. If this happens, there will be buffer overflows, as reported by smatch. Add extra checks to prevent it. While here, remove an unused word = 0 assignment.(CVE-2024-53061)

In the Linux kernel, the following vulnerability has been resolved: media: dvbdev: prevent the risk of out of memory access The dvbdev contains a static variable used to store dvb minors. The behavior of it depends if CONFIG_DVB_DYNAMIC_MINORS is set or not. When not set, dvb_register_device() won't check for boundaries, as it will rely that a previous call to dvb_register_adapter() would already be enforcing it. On a similar way, dvb_device_open() uses the assumption that the register functions already did the needed checks. This can be fragile if some device ends using different calls. This also generate warnings on static check analysers like Coverity. So, add explicit guards to prevent potential risk of OOM issues.(CVE-2024-53063)

In the Linux kernel, the following vulnerability has been resolved: nfs: Fix KMSAN warning in decode_getfattr_attrs() Fix the following KMSAN warning: CPU: 1 UID: 0 PID: 7651 Comm: cp Tainted: G B Tainted: [B]=BAD_PAGE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009) ===================================================== ===================================================== BUG: KMSAN: uninit-value in decode_getfattr_attrs+0x2d6d/0x2f90 decode_getfattr_attrs+0x2d6d/0x2f90 decode_getfattr_generic+0x806/0xb00 nfs4_xdr_dec_getattr+0x1de/0x240 rpcauth_unwrap_resp_decode+0xab/0x100 rpcauth_unwrap_resp+0x95/0xc0 call_decode+0x4ff/0xb50 __rpc_execute+0x57b/0x19d0 rpc_execute+0x368/0x5e0 rpc_run_task+0xcfe/0xee0 nfs4_proc_getattr+0x5b5/0x990 __nfs_revalidate_inode+0x477/0xd00 nfs_access_get_cached+0x1021/0x1cc0 nfs_do_access+0x9f/0xae0 nfs_permission+0x1e4/0x8c0 inode_permission+0x356/0x6c0 link_path_walk+0x958/0x1330 path_lookupat+0xce/0x6b0 filename_lookup+0x23e/0x770 vfs_statx+0xe7/0x970 vfs_fstatat+0x1f2/0x2c0 __se_sys_newfstatat+0x67/0x880 __x64_sys_newfstatat+0xbd/0x120 x64_sys_call+0x1826/0x3cf0 do_syscall_64+0xd0/0x1b0 entry_SYSCALL_64_after_hwframe+0x77/0x7f The KMSAN warning is triggered in decode_getfattr_attrs(), when calling decode_attr_mdsthreshold(). It appears that fattr->mdsthreshold is not initialized. Fix the issue by initializing fattr->mdsthreshold to NULL in nfs_fattr_init().(CVE-2024-53066)

In the Linux kernel, the following vulnerability has been resolved: iio: gts-helper: Fix memory leaks for the error path of iio_gts_build_avail_scale_table() If per_time_scales[i] or per_time_gains[i] kcalloc fails in the for loop of iio_gts_build_avail_scale_table(), the err_free_out will fail to call kfree() each time when i is reduced to 0, so all the per_time_scales[0] and per_time_gains[0] will not be freed, which will cause memory leaks. Fix it by checking if i >= 0.(CVE-2024-53076)

In the Linux kernel, the following vulnerability has been resolved: usb: typec: qcom-pmic: init value of hdr_len/txbuf_len earlier If the read of USB_PDPHY_RX_ACKNOWLEDGE_REG failed, then hdr_len and txbuf_len are uninitialized. This commit stops to print uninitialized value and misleading/false data.(CVE-2024-53083)

In the Linux kernel, the following vulnerability has been resolved: tpm: Lock TPM chip in tpm_pm_suspend() first Setting TPM_CHIP_FLAG_SUSPENDED in the end of tpm_pm_suspend() can be racy according, as this leaves window for tpm_hwrng_read() to be called while the operation is in progress. The recent bug report gives also evidence of this behaviour. Aadress this by locking the TPM chip before checking any chip->flags both in tpm_pm_suspend() and tpm_hwrng_read(). Move TPM_CHIP_FLAG_SUSPENDED check inside tpm_get_random() so that it will be always checked only when the lock is reserved.(CVE-2024-53085)

In the Linux kernel, the following vulnerability has been resolved: LoongArch: KVM: Mark hrtimer to expire in hard interrupt context Like commit 2c0d278f3293f ("KVM: LAPIC: Mark hrtimer to expire in hard interrupt context") and commit 9090825fa9974 ("KVM: arm/arm64: Let the timer expire in hardirq context on RT"), On PREEMPT_RT enabled kernels unmarked hrtimers are moved into soft interrupt expiry mode by default. Then the timers are canceled from an preempt-notifier which is invoked with disabled preemption which is not allowed on PREEMPT_RT. The timer callback is short so in could be invoked in hard-IRQ context. So let the timer expire on hard-IRQ context even on -RT. This fix a "scheduling while atomic" bug for PREEMPT_RT enabled kernels: BUG: scheduling while atomic: qemu-system-loo/1011/0x00000002 Modules linked in: amdgpu rfkill nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat ns CPU: 1 UID: 0 PID: 1011 Comm: qemu-system-loo Tainted: G W 6.12.0-rc2+ #1774 Tainted: [W]=WARN Hardware name: Loongson Loongson-3A5000-7A1000-1w-CRB/Loongson-LS3A5000-7A1000-1w-CRB, BIOS vUDK2018-LoongArch-V2.0.0-prebeta9 10/21/2022 Stack : ffffffffffffffff 0000000000000000 9000000004e3ea38 9000000116744000 90000001167475a0 0000000000000000 90000001167475a8 9000000005644830 90000000058dc000 90000000058dbff8 9000000116747420 0000000000000001 0000000000000001 6a613fc938313980 000000000790c000 90000001001c1140 00000000000003fe 0000000000000001 000000000000000d 0000000000000003 0000000000000030 00000000000003f3 000000000790c000 9000000116747830 90000000057ef000 0000000000000000 9000000005644830 0000000000000004 0000000000000000 90000000057f4b58 0000000000000001 9000000116747868 900000000451b600 9000000005644830 9000000003a13998 0000000010000020 00000000000000b0 0000000000000004 0000000000000000 0000000000071c1d ... Call Trace: [<9000000003a13998>] show_stack+0x38/0x180 [<9000000004e3ea34>] dump_stack_lvl+0x84/0xc0 [<9000000003a71708>] __schedule_bug+0x48/0x60 [<9000000004e45734>] __schedule+0x1114/0x1660 [<9000000004e46040>] schedule_rtlock+0x20/0x60 [<9000000004e4e330>] rtlock_slowlock_locked+0x3f0/0x10a0 [<9000000004e4f038>] rt_spin_lock+0x58/0x80 [<9000000003b02d68>] hrtimer_cancel_wait_running+0x68/0xc0 [<9000000003b02e30>] hrtimer_cancel+0x70/0x80 [<ffff80000235eb70>] kvm_restore_timer+0x50/0x1a0 [kvm] [<ffff8000023616c8>] kvm_arch_vcpu_load+0x68/0x2a0 [kvm] [<ffff80000234c2d4>] kvm_sched_in+0x34/0x60 [kvm] [<9000000003a749a0>] finish_task_switch.isra.0+0x140/0x2e0 [<9000000004e44a70>] __schedule+0x450/0x1660 [<9000000004e45cb0>] schedule+0x30/0x180 [<ffff800002354c70>] kvm_vcpu_block+0x70/0x120 [kvm] [<ffff800002354d80>] kvm_vcpu_halt+0x60/0x3e0 [kvm] [<ffff80000235b194>] kvm_handle_gspr+0x3f4/0x4e0 [kvm] [<ffff80000235f548>] kvm_handle_exit+0x1c8/0x260 kvm

Severity

7.8 (High)


                    
                      CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References

URL

Type

	https://www.openeuler.org/zh/security/security-bu…	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2023-52920	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-45010	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-46698	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-46713	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-46765	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-47678	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-47707	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-47712	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-47745	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-47747	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-47749	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-49856	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-49885	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-49899	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-49914	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-49915	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50024	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50031	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50038	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50039	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50045	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50062	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50085	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50093	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50098	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50141	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50143	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50148	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50154	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50157	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50162	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50166	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50169	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50170	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50171	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50182	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50191	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50192	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50195	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50203	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50205	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50208	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50209	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50216	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50217	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50223	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50230	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50234	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50236	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50241	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50248	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50255	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50258	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50262	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50265	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50269	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50271	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50272	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50273	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50275	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50276	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50283	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50284	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50289	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50294	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50298	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50299	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53043	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53046	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53047	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53052	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53055	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53061	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53063	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53066	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53076	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53083	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53085	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53089	ADVISORY

JSON

To clipboard

{
  "affected": [
    {
      "ecosystem_specific": {
        "aarch64": [
          "bpftool-6.6.0-57.0.0.59.oe2403.aarch64.rpm",
          "bpftool-debuginfo-6.6.0-57.0.0.59.oe2403.aarch64.rpm",
          "kernel-6.6.0-57.0.0.59.oe2403.aarch64.rpm",
          "kernel-debuginfo-6.6.0-57.0.0.59.oe2403.aarch64.rpm",
          "kernel-debugsource-6.6.0-57.0.0.59.oe2403.aarch64.rpm",
          "kernel-devel-6.6.0-57.0.0.59.oe2403.aarch64.rpm",
          "kernel-headers-6.6.0-57.0.0.59.oe2403.aarch64.rpm",
          "kernel-source-6.6.0-57.0.0.59.oe2403.aarch64.rpm",
          "kernel-tools-6.6.0-57.0.0.59.oe2403.aarch64.rpm",
          "kernel-tools-debuginfo-6.6.0-57.0.0.59.oe2403.aarch64.rpm",
          "kernel-tools-devel-6.6.0-57.0.0.59.oe2403.aarch64.rpm",
          "perf-6.6.0-57.0.0.59.oe2403.aarch64.rpm",
          "perf-debuginfo-6.6.0-57.0.0.59.oe2403.aarch64.rpm",
          "python3-perf-6.6.0-57.0.0.59.oe2403.aarch64.rpm",
          "python3-perf-debuginfo-6.6.0-57.0.0.59.oe2403.aarch64.rpm"
        ],
        "src": [
          "kernel-6.6.0-57.0.0.59.oe2403.src.rpm"
        ],
        "x86_64": [
          "bpftool-6.6.0-57.0.0.59.oe2403.x86_64.rpm",
          "bpftool-debuginfo-6.6.0-57.0.0.59.oe2403.x86_64.rpm",
          "kernel-6.6.0-57.0.0.59.oe2403.x86_64.rpm",
          "kernel-debuginfo-6.6.0-57.0.0.59.oe2403.x86_64.rpm",
          "kernel-debugsource-6.6.0-57.0.0.59.oe2403.x86_64.rpm",
          "kernel-devel-6.6.0-57.0.0.59.oe2403.x86_64.rpm",
          "kernel-headers-6.6.0-57.0.0.59.oe2403.x86_64.rpm",
          "kernel-source-6.6.0-57.0.0.59.oe2403.x86_64.rpm",
          "kernel-tools-6.6.0-57.0.0.59.oe2403.x86_64.rpm",
          "kernel-tools-debuginfo-6.6.0-57.0.0.59.oe2403.x86_64.rpm",
          "kernel-tools-devel-6.6.0-57.0.0.59.oe2403.x86_64.rpm",
          "perf-6.6.0-57.0.0.59.oe2403.x86_64.rpm",
          "perf-debuginfo-6.6.0-57.0.0.59.oe2403.x86_64.rpm",
          "python3-perf-6.6.0-57.0.0.59.oe2403.x86_64.rpm",
          "python3-perf-debuginfo-6.6.0-57.0.0.59.oe2403.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:24.03-LTS",
        "name": "kernel",
        "purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-24.03-LTS"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.6.0-57.0.0.59.oe2403"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "severity": "High"
  },
  "details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf: support non-r10 register spill/fill to/from stack in precision tracking  Use instruction (jump) history to record instructions that performed register spill/fill to/from stack, regardless if this was done through read-only r10 register, or any other register after copying r10 into it *and* potentially adjusting offset.  To make this work reliably, we push extra per-instruction flags into instruction history, encoding stack slot index (spi) and stack frame number in extra 10 bit flags we take away from prev_idx in instruction history. We don\u0026apos;t touch idx field for maximum performance, as it\u0026apos;s checked most frequently during backtracking.  This change removes basically the last remaining practical limitation of precision backtracking logic in BPF verifier. It fixes known deficiencies, but also opens up new opportunities to reduce number of verified states, explored in the subsequent patches.  There are only three differences in selftests\u0026apos; BPF object files according to veristat, all in the positive direction (less states).  File                                    Program        Insns (A)  Insns (B)  Insns  (DIFF)  States (A)  States (B)  States (DIFF) --------------------------------------  -------------  ---------  ---------  -------------  ----------  ----------  ------------- test_cls_redirect_dynptr.bpf.linked3.o  cls_redirect        2987       2864  -123 (-4.12%)         240         231    -9 (-3.75%) xdp_synproxy_kern.bpf.linked3.o         syncookie_tc       82848      82661  -187 (-0.23%)        5107        5073   -34 (-0.67%) xdp_synproxy_kern.bpf.linked3.o         syncookie_xdp      85116      84964  -152 (-0.18%)        5162        5130   -32 (-0.62%)  Note, I avoided renaming jmp_history to more generic insn_hist to minimize number of lines changed and potential merge conflicts between bpf and bpf-next trees.  Notice also cur_hist_entry pointer reset to NULL at the beginning of instruction verification loop. This pointer avoids the problem of relying on last jump history entry\u0026apos;s insn_idx to determine whether we already have entry for current instruction or not. It can happen that we added jump history entry because current instruction is_jmp_point(), but also we need to add instruction flags for stack access. In this case, we don\u0026apos;t want to entries, so we need to reuse last added entry, if it is present.  Relying on insn_idx comparison has the same ambiguity problem as the one that was fixed recently in [0], so we avoid that.    [0] https://patchwork.kernel.org/project/netdevbpf/patch/20231110002638.4168352-3-andrii@kernel.org/(CVE-2023-52920)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmptcp: pm: only mark \u0026apos;subflow\u0026apos; endp as available\r\n\r\nAdding the following warning ...\r\n\r\n  WARN_ON_ONCE(msk-\u0026gt;pm.local_addr_used == 0)\r\n\r\n... before decrementing the local_addr_used counter helped to find a bug\nwhen running the \u0026quot;remove single address\u0026quot; subtest from the mptcp_join.sh\nselftests.\r\n\r\nRemoving a \u0026apos;signal\u0026apos; endpoint will trigger the removal of all subflows\nlinked to this endpoint via mptcp_pm_nl_rm_addr_or_subflow() with\nrm_type == MPTCP_MIB_RMSUBFLOW. This will decrement the local_addr_used\ncounter, which is wrong in this case because this counter is linked to\n\u0026apos;subflow\u0026apos; endpoints, and here it is a \u0026apos;signal\u0026apos; endpoint that is being\nremoved.\r\n\r\nNow, the counter is decremented, only if the ID is being used outside\nof mptcp_pm_nl_rm_addr_or_subflow(), only for \u0026apos;subflow\u0026apos; endpoints, and\nif the ID is not 0 -- local_addr_used is not taking into account these\nones. This marking of the ID as being available, and the decrement is\ndone no matter if a subflow using this ID is currently available,\nbecause the subflow could have been closed before.(CVE-2024-45010)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nvideo/aperture: optionally match the device in sysfb_disable()\r\n\r\nIn aperture_remove_conflicting_pci_devices(), we currently only\ncall sysfb_disable() on vga class devices.  This leads to the\nfollowing problem when the pimary device is not VGA compatible:\r\n\r\n1. A PCI device with a non-VGA class is the boot display\n2. That device is probed first and it is not a VGA device so\n   sysfb_disable() is not called, but the device resources\n   are freed by aperture_detach_platform_device()\n3. Non-primary GPU has a VGA class and it ends up calling sysfb_disable()\n4. NULL pointer dereference via sysfb_disable() since the resources\n   have already been freed by aperture_detach_platform_device() when\n   it was called by the other device.\r\n\r\nFix this by passing a device pointer to sysfb_disable() and checking\nthe device to determine if we should execute it or not.\r\n\r\nv2: Fix build when CONFIG_SCREEN_INFO is not set\nv3: Move device check into the mutex\n    Drop primary variable in aperture_remove_conflicting_pci_devices()\n    Drop __init on pci sysfb_pci_dev_is_enabled()(CVE-2024-46698)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nperf/aux: Fix AUX buffer serialization\r\n\r\nOle reported that event-\u0026gt;mmap_mutex is strictly insufficient to\nserialize the AUX buffer, add a per RB mutex to fully serialize it.\r\n\r\nNote that in the lock order comment the perf_event::mmap_mutex order\nwas already wrong, that is, it nesting under mmap_lock is not new with\nthis patch.(CVE-2024-46713)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nice: protect XDP configuration with a mutex\r\n\r\nThe main threat to data consistency in ice_xdp() is a possible asynchronous\nPF reset. It can be triggered by a user or by TX timeout handler.\r\n\r\nXDP setup and PF reset code access the same resources in the following\nsections:\n* ice_vsi_close() in ice_prepare_for_reset() - already rtnl-locked\n* ice_vsi_rebuild() for the PF VSI - not protected\n* ice_vsi_open() - already rtnl-locked\r\n\r\nWith an unfortunate timing, such accesses can result in a crash such as the\none below:\r\n\r\n[ +1.999878] ice 0000:b1:00.0: Registered XDP mem model MEM_TYPE_XSK_BUFF_POOL on Rx ring 14\n[ +2.002992] ice 0000:b1:00.0: Registered XDP mem model MEM_TYPE_XSK_BUFF_POOL on Rx ring 18\n[Mar15 18:17] ice 0000:b1:00.0 ens801f0np0: NETDEV WATCHDOG: CPU: 38: transmit queue 14 timed out 80692736 ms\n[ +0.000093] ice 0000:b1:00.0 ens801f0np0: tx_timeout: VSI_num: 6, Q 14, NTC: 0x0, HW_HEAD: 0x0, NTU: 0x0, INT: 0x4000001\n[ +0.000012] ice 0000:b1:00.0 ens801f0np0: tx_timeout recovery level 1, txqueue 14\n[ +0.394718] ice 0000:b1:00.0: PTP reset successful\n[ +0.006184] BUG: kernel NULL pointer dereference, address: 0000000000000098\n[ +0.000045] #PF: supervisor read access in kernel mode\n[ +0.000023] #PF: error_code(0x0000) - not-present page\n[ +0.000023] PGD 0 P4D 0\n[ +0.000018] Oops: 0000 [#1] PREEMPT SMP NOPTI\n[ +0.000023] CPU: 38 PID: 7540 Comm: kworker/38:1 Not tainted 6.8.0-rc7 #1\n[ +0.000031] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0014.082620210524 08/26/2021\n[ +0.000036] Workqueue: ice ice_service_task [ice]\n[ +0.000183] RIP: 0010:ice_clean_tx_ring+0xa/0xd0 [ice]\n[...]\n[ +0.000013] Call Trace:\n[ +0.000016] \u0026lt;TASK\u0026gt;\n[ +0.000014] ? __die+0x1f/0x70\n[ +0.000029] ? page_fault_oops+0x171/0x4f0\n[ +0.000029] ? schedule+0x3b/0xd0\n[ +0.000027] ? exc_page_fault+0x7b/0x180\n[ +0.000022] ? asm_exc_page_fault+0x22/0x30\n[ +0.000031] ? ice_clean_tx_ring+0xa/0xd0 [ice]\n[ +0.000194] ice_free_tx_ring+0xe/0x60 [ice]\n[ +0.000186] ice_destroy_xdp_rings+0x157/0x310 [ice]\n[ +0.000151] ice_vsi_decfg+0x53/0xe0 [ice]\n[ +0.000180] ice_vsi_rebuild+0x239/0x540 [ice]\n[ +0.000186] ice_vsi_rebuild_by_type+0x76/0x180 [ice]\n[ +0.000145] ice_rebuild+0x18c/0x840 [ice]\n[ +0.000145] ? delay_tsc+0x4a/0xc0\n[ +0.000022] ? delay_tsc+0x92/0xc0\n[ +0.000020] ice_do_reset+0x140/0x180 [ice]\n[ +0.000886] ice_service_task+0x404/0x1030 [ice]\n[ +0.000824] process_one_work+0x171/0x340\n[ +0.000685] worker_thread+0x277/0x3a0\n[ +0.000675] ? preempt_count_add+0x6a/0xa0\n[ +0.000677] ? _raw_spin_lock_irqsave+0x23/0x50\n[ +0.000679] ? __pfx_worker_thread+0x10/0x10\n[ +0.000653] kthread+0xf0/0x120\n[ +0.000635] ? __pfx_kthread+0x10/0x10\n[ +0.000616] ret_from_fork+0x2d/0x50\n[ +0.000612] ? __pfx_kthread+0x10/0x10\n[ +0.000604] ret_from_fork_asm+0x1b/0x30\n[ +0.000604] \u0026lt;/TASK\u0026gt;\r\n\r\nThe previous way of handling this through returning -EBUSY is not viable,\nparticularly when destroying AF_XDP socket, because the kernel proceeds\nwith removal anyway.\r\n\r\nThere is plenty of code between those calls and there is no need to create\na large critical section that covers all of them, same as there is no need\nto protect ice_vsi_rebuild() with rtnl_lock().\r\n\r\nAdd xdp_state_lock mutex to protect ice_vsi_rebuild() and ice_xdp().\r\n\r\nLeaving unprotected sections in between would result in two states that\nhave to be considered:\n1. when the VSI is closed, but not yet rebuild\n2. when VSI is already rebuild, but not yet open\r\n\r\nThe latter case is actually already handled through !netif_running() case,\nwe just need to adjust flag checking a little. The former one is not as\ntrivial, because between ice_vsi_close() and ice_vsi_rebuild(), a lot of\nhardware interaction happens, this can make adding/deleting rings exit\nwith an error. Luckily, VSI rebuild is pending and can apply new\nconfiguration for us in a managed fashion.\r\n\r\nTherefore, add an additional VSI state flag ICE_VSI_REBUILD_PENDING to\nindicate that ice_x\n---truncated---(CVE-2024-46765)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  icmp: change the order of rate limits  ICMP messages are ratelimited :  After the blamed commits, the two rate limiters are applied in this order:  1) host wide ratelimit (icmp_global_allow())  2) Per destination ratelimit (inetpeer based)  In order to avoid side-channels attacks, we need to apply the per destination check first.  This patch makes the following change :  1) icmp_global_allow() checks if the host wide limit is reached.    But credits are not yet consumed. This is deferred to 3)  2) The per destination limit is checked/updated.    This might add a new node in inetpeer tree.  3) icmp_global_consume() consumes tokens if prior operations succeeded.  This means that host wide ratelimit is still effective in keeping inetpeer tree small even under DDOS.  As a bonus, I removed icmp_global.lock as the fast path can use a lock-free operation.(CVE-2024-47678)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ipv6: avoid possible NULL deref in rt6_uncached_list_flush_dev()  Blamed commit accidentally removed a check for rt-\u0026gt;rt6i_idev being NULL, as spotted by syzbot:  Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 1 UID: 0 PID: 10998 Comm: syz-executor Not tainted 6.11.0-rc6-syzkaller-00208-g625403177711 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024  RIP: 0010:rt6_uncached_list_flush_dev net/ipv6/route.c:177 [inline]  RIP: 0010:rt6_disable_ip+0x33e/0x7e0 net/ipv6/route.c:4914 Code: 41 80 3c 04 00 74 0a e8 90 d0 9b f7 48 8b 7c 24 08 48 8b 07 48 89 44 24 10 4c 89 f0 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df \u0026lt;80\u0026gt; 3c 08 00 74 08 4c 89 f7 e8 64 d0 9b f7 48 8b 44 24 18 49 39 06 RSP: 0018:ffffc900047374e0 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 1ffff1100fdf8f33 RCX: dffffc0000000000 RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffff88807efc78c0 RBP: ffffc900047375d0 R08: 0000000000000003 R09: fffff520008e6e8c R10: dffffc0000000000 R11: fffff520008e6e8c R12: 1ffff1100fdf8f18 R13: ffff88807efc7998 R14: 0000000000000000 R15: ffff88807efc7930 FS:  0000000000000000(0000) GS:ffff8880b8900000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020002a80 CR3: 0000000022f62000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;   addrconf_ifdown+0x15d/0x1bd0 net/ipv6/addrconf.c:3856  addrconf_notify+0x3cb/0x1020   notifier_call_chain+0x19f/0x3e0 kernel/notifier.c:93   call_netdevice_notifiers_extack net/core/dev.c:2032 [inline]   call_netdevice_notifiers net/core/dev.c:2046 [inline]   unregister_netdevice_many_notify+0xd81/0x1c40 net/core/dev.c:11352   unregister_netdevice_many net/core/dev.c:11414 [inline]   unregister_netdevice_queue+0x303/0x370 net/core/dev.c:11289   unregister_netdevice include/linux/netdevice.h:3129 [inline]   __tun_detach+0x6b9/0x1600 drivers/net/tun.c:685   tun_detach drivers/net/tun.c:701 [inline]   tun_chr_close+0x108/0x1b0 drivers/net/tun.c:3510   __fput+0x24a/0x8a0 fs/file_table.c:422   task_work_run+0x24f/0x310 kernel/task_work.c:228   exit_task_work include/linux/task_work.h:40 [inline]   do_exit+0xa2f/0x27f0 kernel/exit.c:882   do_group_exit+0x207/0x2c0 kernel/exit.c:1031   __do_sys_exit_group kernel/exit.c:1042 [inline]   __se_sys_exit_group kernel/exit.c:1040 [inline]   __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1040   x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f1acc77def9 Code: Unable to access opcode bytes at 0x7f1acc77decf. RSP: 002b:00007ffeb26fa738 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f1acc77def9 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000043 RBP: 00007f1acc7dd508 R08: 00007ffeb26f84d7 R09: 0000000000000003 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001 R13: 0000000000000003 R14: 00000000ffffffff R15: 00007ffeb26fa8e0  \u0026lt;/TASK\u0026gt; Modules linked in: ---[ end trace 0000000000000000 ]---  RIP: 0010:rt6_uncached_list_flush_dev net/ipv6/route.c:177 [inline]  RIP: 0010:rt6_disable_ip+0x33e/0x7e0 net/ipv6/route.c:4914 Code: 41 80 3c 04 00 74 0a e8 90 d0 9b f7 48 8b 7c 24 08 48 8b 07 48 89 44 24 10 4c 89 f0 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df \u0026lt;80\u0026gt; 3c 08 00 74 08 4c 89 f7 e8 64 d0 9b f7 48 8b 44 24 18 49 39 06 RSP: 0018:ffffc900047374e0 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 1ffff1100fdf8f33 RCX: dffffc0000000000 RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffff88807efc78c0 R ---truncated---(CVE-2024-47707)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param  In the `wilc_parse_join_bss_param` function, the TSF field of the `ies` structure is accessed after the RCU read-side critical section is unlocked. According to RCU usage rules, this is illegal. Reusing this pointer can lead to unpredictable behavior, including accessing memory that has been updated or causing use-after-free issues.  This possible bug was identified using a static analysis tool developed by myself, specifically designed to detect RCU-related issues.  To address this, the TSF value is now stored in a local variable `ies_tsf` before the RCU lock is released. The `param-\u0026gt;tsf_lo` field is then assigned using this local variable, ensuring that the TSF value is safely accessed.(CVE-2024-47712)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  mm: call the security_mmap_file() LSM hook in remap_file_pages()  The remap_file_pages syscall handler calls do_mmap() directly, which doesn\u0026apos;t contain the LSM security check. And if the process has called personality(READ_IMPLIES_EXEC) before and remap_file_pages() is called for RW pages, this will actually result in remapping the pages to RWX, bypassing a W^X policy enforced by SELinux.  So we should check prot by security_mmap_file LSM hook in the remap_file_pages syscall handler before do_mmap() is called. Otherwise, it potentially permits an attacker to bypass a W^X policy enforced by SELinux.  The bypass is similar to CVE-2016-10044, which bypass the same thing via AIO and can be found in [1].  The PoC:  $ cat \u0026gt; test.c  int main(void) {  size_t pagesz = sysconf(_SC_PAGE_SIZE);  int mfd = syscall(SYS_memfd_create, \u0026quot;test\u0026quot;, 0);  const char *buf = mmap(NULL, 4 * pagesz, PROT_READ | PROT_WRITE,   MAP_SHARED, mfd, 0);  unsigned int old = syscall(SYS_personality, 0xffffffff);  syscall(SYS_personality, READ_IMPLIES_EXEC | old);  syscall(SYS_remap_file_pages, buf, pagesz, 0, 2, 0);  syscall(SYS_personality, old);  // show the RWX page exists even if W^X policy is enforced  int fd = open(\u0026quot;/proc/self/maps\u0026quot;, O_RDONLY);  unsigned char buf2[1024];  while (1) {   int ret = read(fd, buf2, 1024);   if (ret \u0026lt;= 0) break;   write(1, buf2, ret);  }  close(fd); }  $ gcc test.c -o test $ ./test | grep rwx 7f1836c34000-7f1836c35000 rwxs 00002000 00:01 2050 /memfd:test (deleted)  [PM: subject line tweaks](CVE-2024-47745)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: seeq: Fix use after free vulnerability in ether3 Driver Due to Race Condition  In the ether3_probe function, a timer is initialized with a callback function ether3_ledoff, bound to \u0026amp;prev(dev)-\u0026gt;timer. Once the timer is started, there is a risk of a race condition if the module or device is removed, triggering the ether3_remove function to perform cleanup. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                    CPU1                        |  ether3_ledoff ether3_remove         |   free_netdev(dev);   |   put_devic           |   kfree(dev);         |  |  ether3_outw(priv(dev)-\u0026gt;regs.config2 |= CFG2_CTRLO, REG_CONFIG2);                       | // use dev  Fix it by ensuring that the timer is canceled before proceeding with the cleanup in ether3_remove.(CVE-2024-47747)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/cxgb4: Added NULL check for lookup_atid  The lookup_atid() function can return NULL if the ATID is invalid or does not exist in the identifier table, which could lead to dereferencing a null pointer without a check in the `act_establish()` and `act_open_rpl()` functions. Add a NULL check to prevent null pointer dereferencing.  Found by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-47749)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  x86/sgx: Fix deadlock in SGX NUMA node search  When the current node doesn\u0026apos;t have an EPC section configured by firmware and all other EPC sections are used up, CPU can get stuck inside the while loop that looks for an available EPC page from remote nodes indefinitely, leading to a soft lockup. Note how nid_of_current will never be equal to nid in that while loop because nid_of_current is not set in sgx_numa_mask.  Also worth mentioning is that it\u0026apos;s perfectly fine for the firmware not to setup an EPC section on a node. While setting up an EPC section on each node can enhance performance, it is not a requirement for functionality.  Rework the loop to start and end on *a* node that has SGX memory. This avoids the deadlock looking for the current SGX-lacking node to show up in the loop when it never will.(CVE-2024-49856)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  mm, slub: avoid zeroing kmalloc redzone  Since commit 946fa0dbf2d8 (\u0026quot;mm/slub: extend redzone check to extra allocated kmalloc space than requested\u0026quot;), setting orig_size treats the wasted space (object_size - orig_size) as a redzone. However with init_on_free=1 we clear the full object-\u0026gt;size, including the redzone.  Additionally we clear the object metadata, including the stored orig_size, making it zero, which makes check_object() treat the whole object as a redzone.  These issues lead to the following BUG report with \u0026quot;slub_debug=FUZ init_on_free=1\u0026quot;:  [    0.000000] ============================================================================= [    0.000000] BUG kmalloc-8 (Not tainted): kmalloc Redzone overwritten [    0.000000] ----------------------------------------------------------------------------- [    0.000000] [    0.000000] 0xffff000010032858-0xffff00001003285f @offset=2136. First byte 0x0 instead of 0xcc [    0.000000] FIX kmalloc-8: Restoring kmalloc Redzone 0xffff000010032858-0xffff00001003285f=0xcc [    0.000000] Slab 0xfffffdffc0400c80 objects=36 used=23 fp=0xffff000010032a18 flags=0x3fffe0000000200(workingset|node=0|zone=0|lastcpupid=0x1ffff) [    0.000000] Object 0xffff000010032858 @offset=2136 fp=0xffff0000100328c8 [    0.000000] [    0.000000] Redzone  ffff000010032850: cc cc cc cc cc cc cc cc                          ........ [    0.000000] Object   ffff000010032858: cc cc cc cc cc cc cc cc                          ........ [    0.000000] Redzone  ffff000010032860: cc cc cc cc cc cc cc cc                          ........ [    0.000000] Padding  ffff0000100328b4: 00 00 00 00 00 00 00 00 00 00 00 00              ............ [    0.000000] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.11.0-rc3-next-20240814-00004-g61844c55c3f4 #144 [    0.000000] Hardware name: NXP i.MX95 19X19 board (DT) [    0.000000] Call trace: [    0.000000]  dump_backtrace+0x90/0xe8 [    0.000000]  show_stack+0x18/0x24 [    0.000000]  dump_stack_lvl+0x74/0x8c [    0.000000]  dump_stack+0x18/0x24 [    0.000000]  print_trailer+0x150/0x218 [    0.000000]  check_object+0xe4/0x454 [    0.000000]  free_to_partial_list+0x2f8/0x5ec  To address the issue, use orig_size to clear the used area. And restore the value of orig_size after clear the remaining area.  When CONFIG_SLUB_DEBUG not defined, (get_orig_size()\u0026apos; directly returns s-\u0026gt;object_size. So when using memset to init the area, the size can simply be orig_size, as orig_size returns object_size when CONFIG_SLUB_DEBUG not enabled. And orig_size can never be bigger than object_size.(CVE-2024-49885)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Initialize denominators\u0026apos; default to 1  [WHAT \u0026amp; HOW] Variables used as denominators and maybe not assigned to other values, should not be 0. Change their default to 1 so they are never 0.  This fixes 10 DIVIDE_BY_ZERO issues reported by Coverity.(CVE-2024-49899)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add null check for pipe_ctx-\u0026gt;plane_state in dcn20_program_pipe  This commit addresses a null pointer dereference issue in the `dcn20_program_pipe` function. The issue could occur when `pipe_ctx-\u0026gt;plane_state` is null.  The fix adds a check to ensure `pipe_ctx-\u0026gt;plane_state` is not null before accessing. This prevents a null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn20/dcn20_hwseq.c:1925 dcn20_program_pipe() error: we previously assumed \u0026apos;pipe_ctx-\u0026gt;plane_state\u0026apos; could be null (see line 1877)(CVE-2024-49914)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add NULL check for clk_mgr in dcn32_init_hw  This commit addresses a potential null pointer dereference issue in the `dcn32_init_hw` function. The issue could occur when `dc-\u0026gt;clk_mgr` is null.  The fix adds a check to ensure `dc-\u0026gt;clk_mgr` is not null before accessing its functions. This prevents a potential null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn32/dcn32_hwseq.c:961 dcn32_init_hw() error: we previously assumed \u0026apos;dc-\u0026gt;clk_mgr\u0026apos; could be null (see line 782)(CVE-2024-49915)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: Fix an unsafe loop on the list  The kernel may crash when deleting a genetlink family if there are still listeners for that family:  Oops: Kernel access of bad area, sig: 11 [#1]   ...   NIP [c000000000c080bc] netlink_update_socket_mc+0x3c/0xc0   LR [c000000000c0f764] __netlink_clear_multicast_users+0x74/0xc0   Call Trace: __netlink_clear_multicast_users+0x74/0xc0 genl_unregister_family+0xd4/0x2d0  Change the unsafe loop on the list to a safe one, because inside the loop there is an element removal from this list.(CVE-2024-50024)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/v3d: Stop the active perfmon before being destroyed  When running `kmscube` with one or more performance monitors enabled via `GALLIUM_HUD`, the following kernel panic can occur:  [   55.008324] Unable to handle kernel paging request at virtual address 00000000052004a4 [   55.008368] Mem abort info: [   55.008377]   ESR = 0x0000000096000005 [   55.008387]   EC = 0x25: DABT (current EL), IL = 32 bits [   55.008402]   SET = 0, FnV = 0 [   55.008412]   EA = 0, S1PTW = 0 [   55.008421]   FSC = 0x05: level 1 translation fault [   55.008434] Data abort info: [   55.008442]   ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000 [   55.008455]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [   55.008467]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [   55.008481] user pgtable: 4k pages, 39-bit VAs, pgdp=00000001046c6000 [   55.008497] [00000000052004a4] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000 [   55.008525] Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP [   55.008542] Modules linked in: rfcomm [...] vc4 v3d snd_soc_hdmi_codec drm_display_helper gpu_sched drm_shmem_helper cec drm_dma_helper drm_kms_helper i2c_brcmstb drm drm_panel_orientation_quirks snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd backlight [   55.008799] CPU: 2 PID: 166 Comm: v3d_bin Tainted: G         C         6.6.47+rpt-rpi-v8 #1  Debian 1:6.6.47-1+rpt1 [   55.008824] Hardware name: Raspberry Pi 4 Model B Rev 1.5 (DT) [   55.008838] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [   55.008855] pc : __mutex_lock.constprop.0+0x90/0x608 [   55.008879] lr : __mutex_lock.constprop.0+0x58/0x608 [   55.008895] sp : ffffffc080673cf0 [   55.008904] x29: ffffffc080673cf0 x28: 0000000000000000 x27: ffffff8106188a28 [   55.008926] x26: ffffff8101e78040 x25: ffffff8101baa6c0 x24: ffffffd9d989f148 [   55.008947] x23: ffffffda1c2a4008 x22: 0000000000000002 x21: ffffffc080673d38 [   55.008968] x20: ffffff8101238000 x19: ffffff8104f83188 x18: 0000000000000000 [   55.008988] x17: 0000000000000000 x16: ffffffda1bd04d18 x15: 00000055bb08bc90 [   55.009715] x14: 0000000000000000 x13: 0000000000000000 x12: ffffffda1bd4cbb0 [   55.010433] x11: 00000000fa83b2da x10: 0000000000001a40 x9 : ffffffda1bd04d04 [   55.011162] x8 : ffffff8102097b80 x7 : 0000000000000000 x6 : 00000000030a5857 [   55.011880] x5 : 00ffffffffffffff x4 : 0300000005200470 x3 : 0300000005200470 [   55.012598] x2 : ffffff8101238000 x1 : 0000000000000021 x0 : 0300000005200470 [   55.013292] Call trace: [   55.013959]  __mutex_lock.constprop.0+0x90/0x608 [   55.014646]  __mutex_lock_slowpath+0x1c/0x30 [   55.015317]  mutex_lock+0x50/0x68 [   55.015961]  v3d_perfmon_stop+0x40/0xe0 [v3d] [   55.016627]  v3d_bin_job_run+0x10c/0x2d8 [v3d] [   55.017282]  drm_sched_main+0x178/0x3f8 [gpu_sched] [   55.017921]  kthread+0x11c/0x128 [   55.018554]  ret_from_fork+0x10/0x20 [   55.019168] Code: f9400260 f1001c1f 54001ea9 927df000 (b9403401) [   55.019776] ---[ end trace 0000000000000000 ]--- [   55.020411] note: v3d_bin[166] exited with preempt_count 1  This issue arises because, upon closing the file descriptor (which happens when we interrupt `kmscube`), the active performance monitor is not stopped. Although all perfmons are destroyed in `v3d_perfmon_close_file()`, the active performance monitor\u0026apos;s pointer (`v3d-\u0026gt;active_perfmon`) is still retained.  If `kmscube` is run again, the driver will attempt to stop the active performance monitor using the stale pointer in `v3d-\u0026gt;active_perfmon`. However, this pointer is no longer valid because the previous process has already terminated, and all performance monitors associated with it have been destroyed and freed.  To fix this, when the active performance monitor belongs to a given process, explicitly stop it before destroying and freeing it.(CVE-2024-50031)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  netfilter: xtables: avoid NFPROTO_UNSPEC where needed  syzbot managed to call xt_cluster match via ebtables:   WARNING: CPU: 0 PID: 11 at net/netfilter/xt_cluster.c:72 xt_cluster_mt+0x196/0x780  [..]  ebt_do_table+0x174b/0x2a40  Module registers to NFPROTO_UNSPEC, but it assumes ipv4/ipv6 packet processing.  As this is only useful to restrict locally terminating TCP/UDP traffic, register this for ipv4 and ipv6 family only.  Pablo points out that this is a general issue, direct users of the set/getsockopt interface can call into targets/matches that were only intended for use with ip(6)tables.  Check all UNSPEC matches and targets for similar issues:  - matches and targets are fine except if they assume skb_network_header()   is valid -- this is only true when called from inet layer: ip(6) stack   pulls the ip/ipv6 header into linear data area. - targets that return XT_CONTINUE or other xtables verdicts must be   restricted too, they are incompatbile with the ebtables traverser, e.g.   EBT_CONTINUE is a completely different value than XT_CONTINUE.  Most matches/targets are changed to register for NFPROTO_IPV4/IPV6, as they are provided for use by ip(6)tables.  The MARK target is also used by arptables, so register for NFPROTO_ARP too.  While at it, bail out if connbytes fails to enable the corresponding conntrack family.  This change passes the selftests in iptables.git.(CVE-2024-50038)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net/sched: accept TCA_STAB only for root qdisc  Most qdiscs maintain their backlog using qdisc_pkt_len(skb) on the assumption it is invariant between the enqueue() and dequeue() handlers.  Unfortunately syzbot can crash a host rather easily using a TBF + SFQ combination, with an STAB on SFQ [1]  We can\u0026apos;t support TCA_STAB on arbitrary level, this would require to maintain per-qdisc storage.  [1] [   88.796496] BUG: kernel NULL pointer dereference, address: 0000000000000000 [   88.798611] #PF: supervisor read access in kernel mode [   88.799014] #PF: error_code(0x0000) - not-present page [   88.799506] PGD 0 P4D 0 [   88.799829] Oops: Oops: 0000 [#1] SMP NOPTI [   88.800569] CPU: 14 UID: 0 PID: 2053 Comm: b371744477 Not tainted 6.12.0-rc1-virtme #1117 [   88.801107] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [   88.801779] RIP: 0010:sfq_dequeue (net/sched/sch_sfq.c:272 net/sched/sch_sfq.c:499) sch_sfq [ 88.802544] Code: 0f b7 50 12 48 8d 04 d5 00 00 00 00 48 89 d6 48 29 d0 48 8b 91 c0 01 00 00 48 c1 e0 03 48 01 c2 66 83 7a 1a 00 7e c0 48 8b 3a \u0026lt;4c\u0026gt; 8b 07 4c 89 02 49 89 50 08 48 c7 47 08 00 00 00 00 48 c7 07 00 All code ========    0: 0f b7 50 12           movzwl 0x12(%rax),%edx    4: 48 8d 04 d5 00 00 00  lea    0x0(,%rdx,8),%rax    b: 00    c: 48 89 d6              mov    %rdx,%rsi    f: 48 29 d0              sub    %rdx,%rax   12: 48 8b 91 c0 01 00 00  mov    0x1c0(%rcx),%rdx   19: 48 c1 e0 03           shl    $0x3,%rax   1d: 48 01 c2              add    %rax,%rdx   20: 66 83 7a 1a 00        cmpw   $0x0,0x1a(%rdx)   25: 7e c0                 jle    0xffffffffffffffe7   27: 48 8b 3a              mov    (%rdx),%rdi   2a:* 4c 8b 07              mov    (%rdi),%r8  \u0026lt;-- trapping instruction   2d: 4c 89 02              mov    %r8,(%rdx)   30: 49 89 50 08           mov    %rdx,0x8(%r8)   34: 48 c7 47 08 00 00 00  movq   $0x0,0x8(%rdi)   3b: 00   3c: 48                    rex.W   3d: c7                    .byte 0xc7   3e: 07                    (bad)  ...  Code starting with the faulting instruction ===========================================    0: 4c 8b 07              mov    (%rdi),%r8    3: 4c 89 02              mov    %r8,(%rdx)    6: 49 89 50 08           mov    %rdx,0x8(%r8)    a: 48 c7 47 08 00 00 00  movq   $0x0,0x8(%rdi)   11: 00   12: 48                    rex.W   13: c7                    .byte 0xc7   14: 07                    (bad)  ... [   88.803721] RSP: 0018:ffff9a1f892b7d58 EFLAGS: 00000206 [   88.804032] RAX: 0000000000000000 RBX: ffff9a1f8420c800 RCX: ffff9a1f8420c800 [   88.804560] RDX: ffff9a1f81bc1440 RSI: 0000000000000000 RDI: 0000000000000000 [   88.805056] RBP: ffffffffc04bb0e0 R08: 0000000000000001 R09: 00000000ff7f9a1f [   88.805473] R10: 000000000001001b R11: 0000000000009a1f R12: 0000000000000140 [   88.806194] R13: 0000000000000001 R14: ffff9a1f886df400 R15: ffff9a1f886df4ac [   88.806734] FS:  00007f445601a740(0000) GS:ffff9a2e7fd80000(0000) knlGS:0000000000000000 [   88.807225] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [   88.807672] CR2: 0000000000000000 CR3: 000000050cc46000 CR4: 00000000000006f0 [   88.808165] Call Trace: [   88.808459]  \u0026lt;TASK\u0026gt; [   88.808710] ? __die (arch/x86/kernel/dumpstack.c:421 arch/x86/kernel/dumpstack.c:434) [   88.809261] ? page_fault_oops (arch/x86/mm/fault.c:715) [   88.809561] ? exc_page_fault (./arch/x86/include/asm/irqflags.h:26 ./arch/x86/include/asm/irqflags.h:87 ./arch/x86/include/asm/irqflags.h:147 arch/x86/mm/fault.c:1489 arch/x86/mm/fault.c:1539) [   88.809806] ? asm_exc_page_fault (./arch/x86/include/asm/idtentry.h:623) [   88.810074] ? sfq_dequeue (net/sched/sch_sfq.c:272 net/sched/sch_sfq.c:499) sch_sfq [   88.810411] sfq_reset (net/sched/sch_sfq.c:525) sch_sfq [   88.810671] qdisc_reset (./include/linux/skbuff.h:2135 ./include/linux/skbuff.h:2441 ./include/linux/skbuff.h:3304 ./include/linux/skbuff.h:3310 net/sched/sch_g ---truncated---(CVE-2024-50039)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  netfilter: br_netfilter: fix panic with metadata_dst skb  Fix a kernel panic in the br_netfilter module when sending untagged traffic via a VxLAN device. This happens during the check for fragmentation in br_nf_dev_queue_xmit.  It is dependent on: 1) the br_netfilter module being loaded; 2) net.bridge.bridge-nf-call-iptables set to 1; 3) a bridge with a VxLAN (single-vxlan-device) netdevice as a bridge port; 4) untagged frames with size higher than the VxLAN MTU forwarded/flooded  When forwarding the untagged packet to the VxLAN bridge port, before the netfilter hooks are called, br_handle_egress_vlan_tunnel is called and changes the skb_dst to the tunnel dst. The tunnel_dst is a metadata type of dst, i.e., skb_valid_dst(skb) is false, and metadata-\u0026gt;dst.dev is NULL.  Then in the br_netfilter hooks, in br_nf_dev_queue_xmit, there\u0026apos;s a check for frames that needs to be fragmented: frames with higher MTU than the VxLAN device end up calling br_nf_ip_fragment, which in turns call ip_skb_dst_mtu.  The ip_dst_mtu tries to use the skb_dst(skb) as if it was a valid dst with valid dst-\u0026gt;dev, thus the crash.  This case was never supported in the first place, so drop the packet instead.  PING 10.0.0.2 (10.0.0.2) from 0.0.0.0 h1-eth0: 2000(2028) bytes of data. [  176.291791] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000110 [  176.292101] Mem abort info: [  176.292184]   ESR = 0x0000000096000004 [  176.292322]   EC = 0x25: DABT (current EL), IL = 32 bits [  176.292530]   SET = 0, FnV = 0 [  176.292709]   EA = 0, S1PTW = 0 [  176.292862]   FSC = 0x04: level 0 translation fault [  176.293013] Data abort info: [  176.293104]   ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 [  176.293488]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [  176.293787]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [  176.293995] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000043ef5000 [  176.294166] [0000000000000110] pgd=0000000000000000, p4d=0000000000000000 [  176.294827] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP [  176.295252] Modules linked in: vxlan ip6_udp_tunnel udp_tunnel veth br_netfilter bridge stp llc ipv6 crct10dif_ce [  176.295923] CPU: 0 PID: 188 Comm: ping Not tainted 6.8.0-rc3-g5b3fbd61b9d1 #2 [  176.296314] Hardware name: linux,dummy-virt (DT) [  176.296535] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [  176.296808] pc : br_nf_dev_queue_xmit+0x390/0x4ec [br_netfilter] [  176.297382] lr : br_nf_dev_queue_xmit+0x2ac/0x4ec [br_netfilter] [  176.297636] sp : ffff800080003630 [  176.297743] x29: ffff800080003630 x28: 0000000000000008 x27: ffff6828c49ad9f8 [  176.298093] x26: ffff6828c49ad000 x25: 0000000000000000 x24: 00000000000003e8 [  176.298430] x23: 0000000000000000 x22: ffff6828c4960b40 x21: ffff6828c3b16d28 [  176.298652] x20: ffff6828c3167048 x19: ffff6828c3b16d00 x18: 0000000000000014 [  176.298926] x17: ffffb0476322f000 x16: ffffb7e164023730 x15: 0000000095744632 [  176.299296] x14: ffff6828c3f1c880 x13: 0000000000000002 x12: ffffb7e137926a70 [  176.299574] x11: 0000000000000001 x10: ffff6828c3f1c898 x9 : 0000000000000000 [  176.300049] x8 : ffff6828c49bf070 x7 : 0008460f18d5f20e x6 : f20e0100bebafeca [  176.300302] x5 : ffff6828c7f918fe x4 : ffff6828c49bf070 x3 : 0000000000000000 [  176.300586] x2 : 0000000000000000 x1 : ffff6828c3c7ad00 x0 : ffff6828c7f918f0 [  176.300889] Call trace: [  176.301123]  br_nf_dev_queue_xmit+0x390/0x4ec [br_netfilter] [  176.301411]  br_nf_post_routing+0x2a8/0x3e4 [br_netfilter] [  176.301703]  nf_hook_slow+0x48/0x124 [  176.302060]  br_forward_finish+0xc8/0xe8 [bridge] [  176.302371]  br_nf_hook_thresh+0x124/0x134 [br_netfilter] [  176.302605]  br_nf_forward_finish+0x118/0x22c [br_netfilter] [  176.302824]  br_nf_forward_ip.part.0+0x264/0x290 [br_netfilter] [  176.303136]  br_nf_forward+0x2b8/0x4e0 [br_netfilter] [  176.303359]  nf_hook_slow+0x48/0x124 [  176.303 ---truncated---(CVE-2024-50045)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/rtrs-srv: Avoid null pointer deref during path establishment  For RTRS path establishment, RTRS client initiates and completes con_num of connections. After establishing all its connections, the information is exchanged between the client and server through the info_req message. During this exchange, it is essential that all connections have been established, and the state of the RTRS srv path is CONNECTED.  So add these sanity checks, to make sure we detect and abort process in error scenarios to avoid null pointer deref.(CVE-2024-50062)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  mptcp: pm: fix UaF read in mptcp_pm_nl_rm_addr_or_subflow  Syzkaller reported this splat:    ==================================================================   BUG: KASAN: slab-use-after-free in mptcp_pm_nl_rm_addr_or_subflow+0xb44/0xcc0 net/mptcp/pm_netlink.c:881   Read of size 4 at addr ffff8880569ac858 by task syz.1.2799/14662    CPU: 0 UID: 0 PID: 14662 Comm: syz.1.2799 Not tainted 6.12.0-rc2-syzkaller-00307-g36c254515dc6 #0   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014   Call Trace:    \u0026lt;TASK\u0026gt;    __dump_stack lib/dump_stack.c:94 [inline]    dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120    print_address_description mm/kasan/report.c:377 [inline]    print_report+0xc3/0x620 mm/kasan/report.c:488    kasan_report+0xd9/0x110 mm/kasan/report.c:601    mptcp_pm_nl_rm_addr_or_subflow+0xb44/0xcc0 net/mptcp/pm_netlink.c:881    mptcp_pm_nl_rm_subflow_received net/mptcp/pm_netlink.c:914 [inline]    mptcp_nl_remove_id_zero_address+0x305/0x4a0 net/mptcp/pm_netlink.c:1572    mptcp_pm_nl_del_addr_doit+0x5c9/0x770 net/mptcp/pm_netlink.c:1603    genl_family_rcv_msg_doit+0x202/0x2f0 net/netlink/genetlink.c:1115    genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]    genl_rcv_msg+0x565/0x800 net/netlink/genetlink.c:1210    netlink_rcv_skb+0x165/0x410 net/netlink/af_netlink.c:2551    genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219    netlink_unicast_kernel net/netlink/af_netlink.c:1331 [inline]    netlink_unicast+0x53c/0x7f0 net/netlink/af_netlink.c:1357    netlink_sendmsg+0x8b8/0xd70 net/netlink/af_netlink.c:1901    sock_sendmsg_nosec net/socket.c:729 [inline]    __sock_sendmsg net/socket.c:744 [inline]    ____sys_sendmsg+0x9ae/0xb40 net/socket.c:2607    ___sys_sendmsg+0x135/0x1e0 net/socket.c:2661    __sys_sendmsg+0x117/0x1f0 net/socket.c:2690    do_syscall_32_irqs_on arch/x86/entry/common.c:165 [inline]    __do_fast_syscall_32+0x73/0x120 arch/x86/entry/common.c:386    do_fast_syscall_32+0x32/0x80 arch/x86/entry/common.c:411    entry_SYSENTER_compat_after_hwframe+0x84/0x8e   RIP: 0023:0xf7fe4579   Code: b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 00 00 00 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 \u0026lt;5d\u0026gt; 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00   RSP: 002b:00000000f574556c EFLAGS: 00000296 ORIG_RAX: 0000000000000172   RAX: ffffffffffffffda RBX: 000000000000000b RCX: 0000000020000140   RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000   RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000   R10: 0000000000000000 R11: 0000000000000296 R12: 0000000000000000   R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000    \u0026lt;/TASK\u0026gt;    Allocated by task 5387:    kasan_save_stack+0x33/0x60 mm/kasan/common.c:47    kasan_save_track+0x14/0x30 mm/kasan/common.c:68    poison_kmalloc_redzone mm/kasan/common.c:377 [inline]    __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:394    kmalloc_noprof include/linux/slab.h:878 [inline]    kzalloc_noprof include/linux/slab.h:1014 [inline]    subflow_create_ctx+0x87/0x2a0 net/mptcp/subflow.c:1803    subflow_ulp_init+0xc3/0x4d0 net/mptcp/subflow.c:1956    __tcp_set_ulp net/ipv4/tcp_ulp.c:146 [inline]    tcp_set_ulp+0x326/0x7f0 net/ipv4/tcp_ulp.c:167    mptcp_subflow_create_socket+0x4ae/0x10a0 net/mptcp/subflow.c:1764    __mptcp_subflow_connect+0x3cc/0x1490 net/mptcp/subflow.c:1592    mptcp_pm_create_subflow_or_signal_addr+0xbda/0x23a0 net/mptcp/pm_netlink.c:642    mptcp_pm_nl_fully_established net/mptcp/pm_netlink.c:650 [inline]    mptcp_pm_nl_work+0x3a1/0x4f0 net/mptcp/pm_netlink.c:943    mptcp_worker+0x15a/0x1240 net/mptcp/protocol.c:2777    process_one_work+0x958/0x1b30 kernel/workqueue.c:3229    process_scheduled_works kernel/workqueue.c:3310 [inline]    worker_thread+0x6c8/0xf00 kernel/workqueue.c:3391    kthread+0x2c1/0x3a0 kernel/kthread.c:389    ret_from_fork+0x45/0x80 arch/x86/ke ---truncated---(CVE-2024-50085)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  thermal: intel: int340x: processor: Fix warning during module unload  The processor_thermal driver uses pcim_device_enable() to enable a PCI device, which means the device will be automatically disabled on driver detach.  Thus there is no need to call pci_disable_device() again on it.  With recent PCI device resource management improvements, e.g. commit f748a07a0b64 (\u0026quot;PCI: Remove legacy pcim_release()\u0026quot;), this problem is exposed and triggers the warining below.   [  224.010735] proc_thermal_pci 0000:00:04.0: disabling already-disabled device  [  224.010747] WARNING: CPU: 8 PID: 4442 at drivers/pci/pci.c:2250 pci_disable_device+0xe5/0x100  ...  [  224.010844] Call Trace:  [  224.010845]  \u0026lt;TASK\u0026gt;  [  224.010847]  ? show_regs+0x6d/0x80  [  224.010851]  ? __warn+0x8c/0x140  [  224.010854]  ? pci_disable_device+0xe5/0x100  [  224.010856]  ? report_bug+0x1c9/0x1e0  [  224.010859]  ? handle_bug+0x46/0x80  [  224.010862]  ? exc_invalid_op+0x1d/0x80  [  224.010863]  ? asm_exc_invalid_op+0x1f/0x30  [  224.010867]  ? pci_disable_device+0xe5/0x100  [  224.010869]  ? pci_disable_device+0xe5/0x100  [  224.010871]  ? kfree+0x21a/0x2b0  [  224.010873]  pcim_disable_device+0x20/0x30  [  224.010875]  devm_action_release+0x16/0x20  [  224.010878]  release_nodes+0x47/0xc0  [  224.010880]  devres_release_all+0x9f/0xe0  [  224.010883]  device_unbind_cleanup+0x12/0x80  [  224.010885]  device_release_driver_internal+0x1ca/0x210  [  224.010887]  driver_detach+0x4e/0xa0  [  224.010889]  bus_remove_driver+0x6f/0xf0  [  224.010890]  driver_unregister+0x35/0x60  [  224.010892]  pci_unregister_driver+0x44/0x90  [  224.010894]  proc_thermal_pci_driver_exit+0x14/0x5f0 [processor_thermal_device_pci]  ...  [  224.010921] ---[ end trace 0000000000000000 ]---  Remove the excess pci_disable_device() calls.  [ rjw: Subject and changelog edits ](CVE-2024-50093)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  scsi: ufs: core: Set SDEV_OFFLINE when UFS is shut down  There is a history of deadlock if reboot is performed at the beginning of booting. SDEV_QUIESCE was set for all LU\u0026apos;s scsi_devices by UFS shutdown, and at that time the audio driver was waiting on blk_mq_submit_bio() holding a mutex_lock while reading the fw binary. After that, a deadlock issue occurred while audio driver shutdown was waiting for mutex_unlock of blk_mq_submit_bio(). To solve this, set SDEV_OFFLINE for all LUs except WLUN, so that any I/O that comes down after a UFS shutdown will return an error.  [   31.907781]I[0:      swapper/0:    0]        1        130705007       1651079834      11289729804                0 D(   2) 3 ffffff882e208000 *             init [device_shutdown] [   31.907793]I[0:      swapper/0:    0] Mutex: 0xffffff8849a2b8b0: owner[0xffffff882e28cb00 kworker/6:0 :49] [   31.907806]I[0:      swapper/0:    0] Call trace: [   31.907810]I[0:      swapper/0:    0]  __switch_to+0x174/0x338 [   31.907819]I[0:      swapper/0:    0]  __schedule+0x5ec/0x9cc [   31.907826]I[0:      swapper/0:    0]  schedule+0x7c/0xe8 [   31.907834]I[0:      swapper/0:    0]  schedule_preempt_disabled+0x24/0x40 [   31.907842]I[0:      swapper/0:    0]  __mutex_lock+0x408/0xdac [   31.907849]I[0:      swapper/0:    0]  __mutex_lock_slowpath+0x14/0x24 [   31.907858]I[0:      swapper/0:    0]  mutex_lock+0x40/0xec [   31.907866]I[0:      swapper/0:    0]  device_shutdown+0x108/0x280 [   31.907875]I[0:      swapper/0:    0]  kernel_restart+0x4c/0x11c [   31.907883]I[0:      swapper/0:    0]  __arm64_sys_reboot+0x15c/0x280 [   31.907890]I[0:      swapper/0:    0]  invoke_syscall+0x70/0x158 [   31.907899]I[0:      swapper/0:    0]  el0_svc_common+0xb4/0xf4 [   31.907909]I[0:      swapper/0:    0]  do_el0_svc+0x2c/0xb0 [   31.907918]I[0:      swapper/0:    0]  el0_svc+0x34/0xe0 [   31.907928]I[0:      swapper/0:    0]  el0t_64_sync_handler+0x68/0xb4 [   31.907937]I[0:      swapper/0:    0]  el0t_64_sync+0x1a0/0x1a4  [   31.908774]I[0:      swapper/0:    0]       49                0         11960702      11236868007                0 D(   2) 6 ffffff882e28cb00 *      kworker/6:0 [__bio_queue_enter] [   31.908783]I[0:      swapper/0:    0] Call trace: [   31.908788]I[0:      swapper/0:    0]  __switch_to+0x174/0x338 [   31.908796]I[0:      swapper/0:    0]  __schedule+0x5ec/0x9cc [   31.908803]I[0:      swapper/0:    0]  schedule+0x7c/0xe8 [   31.908811]I[0:      swapper/0:    0]  __bio_queue_enter+0xb8/0x178 [   31.908818]I[0:      swapper/0:    0]  blk_mq_submit_bio+0x194/0x67c [   31.908827]I[0:      swapper/0:    0]  __submit_bio+0xb8/0x19c(CVE-2024-50098)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ACPI: PRM: Find EFI_MEMORY_RUNTIME block for PRM handler and context  PRMT needs to find the correct type of block to translate the PA-VA mapping for EFI runtime services.  The issue arises because the PRMT is finding a block of type EFI_CONVENTIONAL_MEMORY, which is not appropriate for runtime services as described in Section 2.2.2 (Runtime Services) of the UEFI Specification [1]. Since the PRM handler is a type of runtime service, this causes an exception when the PRM handler is called.      [Firmware Bug]: Unable to handle paging request in EFI runtime service     WARNING: CPU: 22 PID: 4330 at drivers/firmware/efi/runtime-wrappers.c:341         __efi_queue_work+0x11c/0x170     Call trace:  Let PRMT find a block with EFI_MEMORY_RUNTIME for PRM handler and PRM context.  If no suitable block is found, a warning message will be printed, but the procedure continues to manage the next PRM handler.  However, if the PRM handler is actually called without proper allocation, it would result in a failure during error handling.  By using the correct memory types for runtime services, ensure that the PRM handler and the context are properly mapped in the virtual address space during runtime, preventing the paging request error.  The issue is really that only memory that has been remapped for runtime by the firmware can be used by the PRM handler, and so the region needs to have the EFI_MEMORY_RUNTIME attribute.  [ rjw: Subject and changelog edits ](CVE-2024-50141)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  udf: fix uninit-value use in udf_get_fileshortad  Check for overflow when computing alen in udf_current_aext to mitigate later uninit-value use in udf_get_fileshortad KMSAN bug[1]. After applying the patch reproducer did not trigger any issue[2].  [1] https://syzkaller.appspot.com/bug?extid=8901c4560b7ab5c2f9df [2] https://syzkaller.appspot.com/x/log.txt?x=10242227980000(CVE-2024-50143)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  Bluetooth: bnep: fix wild-memory-access in proto_unregister  There\u0026apos;s issue as follows:   KASAN: maybe wild-memory-access in range [0xdead...108-0xdead...10f]   CPU: 3 UID: 0 PID: 2805 Comm: rmmod Tainted: G        W   RIP: 0010:proto_unregister+0xee/0x400   Call Trace:    \u0026lt;TASK\u0026gt;    __do_sys_delete_module+0x318/0x580    do_syscall_64+0xc1/0x1d0    entry_SYSCALL_64_after_hwframe+0x77/0x7f  As bnep_init() ignore bnep_sock_init()\u0026apos;s return value, and bnep_sock_init() will cleanup all resource. Then when remove bnep module will call bnep_sock_cleanup() to cleanup sock\u0026apos;s resource. To solve above issue just return bnep_sock_init()\u0026apos;s return value in bnep_exit().(CVE-2024-50148)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tcp/dccp: Don\u0026apos;t use timer_pending() in reqsk_queue_unlink().  Martin KaFai Lau reported use-after-free [0] in reqsk_timer_handler().    \u0026quot;\u0026quot;\u0026quot;   We are seeing a use-after-free from a bpf prog attached to   trace_tcp_retransmit_synack. The program passes the req-\u0026gt;sk to the   bpf_sk_storage_get_tracing kernel helper which does check for null   before using it.   \u0026quot;\u0026quot;\u0026quot;  The commit 83fccfc3940c (\u0026quot;inet: fix potential deadlock in reqsk_queue_unlink()\u0026quot;) added timer_pending() in reqsk_queue_unlink() not to call del_timer_sync() from reqsk_timer_handler(), but it introduced a small race window.  Before the timer is called, expire_timers() calls detach_timer(timer, true) to clear timer-\u0026gt;entry.pprev and marks it as not pending.  If reqsk_queue_unlink() checks timer_pending() just after expire_timers() calls detach_timer(), TCP will miss del_timer_sync(); the reqsk timer will continue running and send multiple SYN+ACKs until it expires.  The reported UAF could happen if req-\u0026gt;sk is close()d earlier than the timer expiration, which is 63s by default.  The scenario would be    1. inet_csk_complete_hashdance() calls inet_csk_reqsk_queue_drop(),      but del_timer_sync() is missed    2. reqsk timer is executed and scheduled again    3. req-\u0026gt;sk is accept()ed and reqsk_put() decrements rsk_refcnt, but      reqsk timer still has another one, and inet_csk_accept() does not      clear req-\u0026gt;sk for non-TFO sockets    4. sk is close()d    5. reqsk timer is executed again, and BPF touches req-\u0026gt;sk  Let\u0026apos;s not use timer_pending() by passing the caller context to __inet_csk_reqsk_queue_drop().  Note that reqsk timer is pinned, so the issue does not happen in most use cases. [1]  [0] BUG: KFENCE: use-after-free read in bpf_sk_storage_get_tracing+0x2e/0x1b0  Use-after-free read at 0x00000000a891fb3a (in kfence-#1): bpf_sk_storage_get_tracing+0x2e/0x1b0 bpf_prog_5ea3e95db6da0438_tcp_retransmit_synack+0x1d20/0x1dda bpf_trace_run2+0x4c/0xc0 tcp_rtx_synack+0xf9/0x100 reqsk_timer_handler+0xda/0x3d0 run_timer_softirq+0x292/0x8a0 irq_exit_rcu+0xf5/0x320 sysvec_apic_timer_interrupt+0x6d/0x80 asm_sysvec_apic_timer_interrupt+0x16/0x20 intel_idle_irq+0x5a/0xa0 cpuidle_enter_state+0x94/0x273 cpu_startup_entry+0x15e/0x260 start_secondary+0x8a/0x90 secondary_startup_64_no_verify+0xfa/0xfb  kfence-#1: 0x00000000a72cc7b6-0x00000000d97616d9, size=2376, cache=TCPv6  allocated by task 0 on cpu 9 at 260507.901592s: sk_prot_alloc+0x35/0x140 sk_clone_lock+0x1f/0x3f0 inet_csk_clone_lock+0x15/0x160 tcp_create_openreq_child+0x1f/0x410 tcp_v6_syn_recv_sock+0x1da/0x700 tcp_check_req+0x1fb/0x510 tcp_v6_rcv+0x98b/0x1420 ipv6_list_rcv+0x2258/0x26e0 napi_complete_done+0x5b1/0x2990 mlx5e_napi_poll+0x2ae/0x8d0 net_rx_action+0x13e/0x590 irq_exit_rcu+0xf5/0x320 common_interrupt+0x80/0x90 asm_common_interrupt+0x22/0x40 cpuidle_enter_state+0xfb/0x273 cpu_startup_entry+0x15e/0x260 start_secondary+0x8a/0x90 secondary_startup_64_no_verify+0xfa/0xfb  freed by task 0 on cpu 9 at 260507.927527s: rcu_core_si+0x4ff/0xf10 irq_exit_rcu+0xf5/0x320 sysvec_apic_timer_interrupt+0x6d/0x80 asm_sysvec_apic_timer_interrupt+0x16/0x20 cpuidle_enter_state+0xfb/0x273 cpu_startup_entry+0x15e/0x260 start_secondary+0x8a/0x90 secondary_startup_64_no_verify+0xfa/0xfb(CVE-2024-50154)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/bnxt_re: Avoid CPU lockups due fifo occupancy check loop  Driver waits indefinitely for the fifo occupancy to go below a threshold as soon as the pacing interrupt is received. This can cause soft lockup on one of the processors, if the rate of DB is very high.  Add a loop count for FPGA and exit the __wait_for_fifo_occupancy_below_th if the loop is taking more time. Pacing will be continuing until the occupancy is below the threshold. This is ensured by the checks in bnxt_re_pacing_timer_exp and further scheduling the work for pacing based on the fifo occupancy.(CVE-2024-50157)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf: devmap: provide rxq after redirect  rxq contains a pointer to the device from where the redirect happened. Currently, the BPF program that was executed after a redirect via BPF_MAP_TYPE_DEVMAP* does not have it set.  This is particularly bad since accessing ingress_ifindex, e.g.  SEC(\u0026quot;xdp\u0026quot;) int prog(struct xdp_md *pkt) {         return bpf_redirect_map(\u0026amp;dev_redirect_map, 0, 0); }  SEC(\u0026quot;xdp/devmap\u0026quot;) int prog_after_redirect(struct xdp_md *pkt) {         bpf_printk(\u0026quot;ifindex %i\u0026quot;, pkt-\u0026gt;ingress_ifindex);         return XDP_PASS; }  depends on access to rxq, so a NULL pointer gets dereferenced:  \u0026lt;1\u0026gt;[  574.475170] BUG: kernel NULL pointer dereference, address: 0000000000000000 \u0026lt;1\u0026gt;[  574.475188] #PF: supervisor read access in kernel mode \u0026lt;1\u0026gt;[  574.475194] #PF: error_code(0x0000) - not-present page \u0026lt;6\u0026gt;[  574.475199] PGD 0 P4D 0 \u0026lt;4\u0026gt;[  574.475207] Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI \u0026lt;4\u0026gt;[  574.475217] CPU: 4 UID: 0 PID: 217 Comm: kworker/4:1 Not tainted 6.11.0-rc5-reduced-00859-g780801200300 #23 \u0026lt;4\u0026gt;[  574.475226] Hardware name: Intel(R) Client Systems NUC13ANHi7/NUC13ANBi7, BIOS ANRPL357.0026.2023.0314.1458 03/14/2023 \u0026lt;4\u0026gt;[  574.475231] Workqueue: mld mld_ifc_work \u0026lt;4\u0026gt;[  574.475247] RIP: 0010:bpf_prog_5e13354d9cf5018a_prog_after_redirect+0x17/0x3c \u0026lt;4\u0026gt;[  574.475257] Code: cc cc cc cc cc cc cc 80 00 00 00 cc cc cc cc cc cc cc cc f3 0f 1e fa 0f 1f 44 00 00 66 90 55 48 89 e5 f3 0f 1e fa 48 8b 57 20 \u0026lt;48\u0026gt; 8b 52 00 8b 92 e0 00 00 00 48 bf f8 a6 d5 c4 5d a0 ff ff be 0b \u0026lt;4\u0026gt;[  574.475263] RSP: 0018:ffffa62440280c98 EFLAGS: 00010206 \u0026lt;4\u0026gt;[  574.475269] RAX: ffffa62440280cd8 RBX: 0000000000000001 RCX: 0000000000000000 \u0026lt;4\u0026gt;[  574.475274] RDX: 0000000000000000 RSI: ffffa62440549048 RDI: ffffa62440280ce0 \u0026lt;4\u0026gt;[  574.475278] RBP: ffffa62440280c98 R08: 0000000000000002 R09: 0000000000000001 \u0026lt;4\u0026gt;[  574.475281] R10: ffffa05dc8b98000 R11: ffffa05f577fca40 R12: ffffa05dcab24000 \u0026lt;4\u0026gt;[  574.475285] R13: ffffa62440280ce0 R14: ffffa62440549048 R15: ffffa62440549000 \u0026lt;4\u0026gt;[  574.475289] FS:  0000000000000000(0000) GS:ffffa05f4f700000(0000) knlGS:0000000000000000 \u0026lt;4\u0026gt;[  574.475294] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 \u0026lt;4\u0026gt;[  574.475298] CR2: 0000000000000000 CR3: 000000025522e000 CR4: 0000000000f50ef0 \u0026lt;4\u0026gt;[  574.475303] PKRU: 55555554 \u0026lt;4\u0026gt;[  574.475306] Call Trace: \u0026lt;4\u0026gt;[  574.475313]  \u0026lt;IRQ\u0026gt; \u0026lt;4\u0026gt;[  574.475318]  ? __die+0x23/0x70 \u0026lt;4\u0026gt;[  574.475329]  ? page_fault_oops+0x180/0x4c0 \u0026lt;4\u0026gt;[  574.475339]  ? skb_pp_cow_data+0x34c/0x490 \u0026lt;4\u0026gt;[  574.475346]  ? kmem_cache_free+0x257/0x280 \u0026lt;4\u0026gt;[  574.475357]  ? exc_page_fault+0x67/0x150 \u0026lt;4\u0026gt;[  574.475368]  ? asm_exc_page_fault+0x26/0x30 \u0026lt;4\u0026gt;[  574.475381]  ? bpf_prog_5e13354d9cf5018a_prog_after_redirect+0x17/0x3c \u0026lt;4\u0026gt;[  574.475386]  bq_xmit_all+0x158/0x420 \u0026lt;4\u0026gt;[  574.475397]  __dev_flush+0x30/0x90 \u0026lt;4\u0026gt;[  574.475407]  veth_poll+0x216/0x250 [veth] \u0026lt;4\u0026gt;[  574.475421]  __napi_poll+0x28/0x1c0 \u0026lt;4\u0026gt;[  574.475430]  net_rx_action+0x32d/0x3a0 \u0026lt;4\u0026gt;[  574.475441]  handle_softirqs+0xcb/0x2c0 \u0026lt;4\u0026gt;[  574.475451]  do_softirq+0x40/0x60 \u0026lt;4\u0026gt;[  574.475458]  \u0026lt;/IRQ\u0026gt; \u0026lt;4\u0026gt;[  574.475461]  \u0026lt;TASK\u0026gt; \u0026lt;4\u0026gt;[  574.475464]  __local_bh_enable_ip+0x66/0x70 \u0026lt;4\u0026gt;[  574.475471]  __dev_queue_xmit+0x268/0xe40 \u0026lt;4\u0026gt;[  574.475480]  ? selinux_ip_postroute+0x213/0x420 \u0026lt;4\u0026gt;[  574.475491]  ? alloc_skb_with_frags+0x4a/0x1d0 \u0026lt;4\u0026gt;[  574.475502]  ip6_finish_output2+0x2be/0x640 \u0026lt;4\u0026gt;[  574.475512]  ? nf_hook_slow+0x42/0xf0 \u0026lt;4\u0026gt;[  574.475521]  ip6_finish_output+0x194/0x300 \u0026lt;4\u0026gt;[  574.475529]  ? __pfx_ip6_finish_output+0x10/0x10 \u0026lt;4\u0026gt;[  574.475538]  mld_sendpack+0x17c/0x240 \u0026lt;4\u0026gt;[  574.475548]  mld_ifc_work+0x192/0x410 \u0026lt;4\u0026gt;[  574.475557]  process_one_work+0x15d/0x380 \u0026lt;4\u0026gt;[  574.475566]  worker_thread+0x29d/0x3a0 \u0026lt;4\u0026gt;[  574.475573]  ? __pfx_worker_thread+0x10/0x10 \u0026lt;4\u0026gt;[  574.475580]  ? __pfx_worker_thread+0x10/0x10 \u0026lt;4\u0026gt;[  574.475587]  kthread+0xcd/0x100 \u0026lt;4\u0026gt;[  574.475597]  ? __pfx_kthread+0x10/0x10 \u0026lt;4\u0026gt;[  574.475606]  ret_from_fork+0x31/0x50 \u0026lt;4\u0026gt;[  574.475615]  ? __pfx_kthread+0x10/0x10 \u0026lt;4\u0026gt;[  574.475623]  ret_from_fork_asm+0x1a/0x ---truncated---(CVE-2024-50162)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  fsl/fman: Fix refcount handling of fman-related devices  In mac_probe() there are multiple calls to of_find_device_by_node(), fman_bind() and fman_port_bind() which takes references to of_dev-\u0026gt;dev. Not all references taken by these calls are released later on error path in mac_probe() and in mac_remove() which lead to reference leaks.  Add references release.(CVE-2024-50166)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  vsock: Update rx_bytes on read_skb()  Make sure virtio_transport_inc_rx_pkt() and virtio_transport_dec_rx_pkt() calls are balanced (i.e. virtio_vsock_sock::rx_bytes doesn\u0026apos;t lie) after vsock_transport::read_skb().  While here, also inform the peer that we\u0026apos;ve freed up space and it has more credit.  Failing to update rx_bytes after packet is dequeued leads to a warning on SOCK_STREAM recv():  [  233.396654] rx_queue is empty, but rx_bytes is non-zero [  233.396702] WARNING: CPU: 11 PID: 40601 at net/vmw_vsock/virtio_transport_common.c:589(CVE-2024-50169)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: bcmasp: fix potential memory leak in bcmasp_xmit()  The bcmasp_xmit() returns NETDEV_TX_OK without freeing skb in case of mapping fails, add dev_kfree_skb() to fix it.(CVE-2024-50170)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: systemport: fix potential memory leak in bcm_sysport_xmit()  The bcm_sysport_xmit() returns NETDEV_TX_OK without freeing skb in case of dma_map_single() fails, add dev_kfree_skb() to fix it.(CVE-2024-50171)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  secretmem: disable memfd_secret() if arch cannot set direct map  Return -ENOSYS from memfd_secret() syscall if !can_set_direct_map().  This is the case for example on some arm64 configurations, where marking 4k PTEs in the direct map not present can only be done if the direct map is set up at 4k granularity in the first place (as ARM\u0026apos;s break-before-make semantics do not easily allow breaking apart large/gigantic pages).  More precisely, on arm64 systems with !can_set_direct_map(), set_direct_map_invalid_noflush() is a no-op, however it returns success (0) instead of an error.  This means that memfd_secret will seemingly \u0026quot;work\u0026quot; (e.g.  syscall succeeds, you can mmap the fd and fault in pages), but it does not actually achieve its goal of removing its memory from the direct map.  Note that with this patch, memfd_secret() will start erroring on systems where can_set_direct_map() returns false (arm64 with CONFIG_RODATA_FULL_DEFAULT_ENABLED=n, CONFIG_DEBUG_PAGEALLOC=n and CONFIG_KFENCE=n), but that still seems better than the current silent failure.  Since CONFIG_RODATA_FULL_DEFAULT_ENABLED defaults to \u0026apos;y\u0026apos;, most arm64 systems actually have a working memfd_secret() and aren\u0026apos;t be affected.  From going through the iterations of the original memfd_secret patch series, it seems that disabling the syscall in these scenarios was the intended behavior [1] (preferred over having set_direct_map_invalid_noflush return an error as that would result in SIGBUSes at page-fault time), however the check for it got dropped between v16 [2] and v17 [3], when secretmem moved away from CMA allocations.  [1]: https://lore.kernel.org/lkml/20201124164930.GK8537@kernel.org/ [2]: https://lore.kernel.org/lkml/20210121122723.3446-11-rppt@kernel.org/#t [3]: https://lore.kernel.org/lkml/20201125092208.12544-10-rppt@kernel.org/(CVE-2024-50182)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: don\u0026apos;t set SB_RDONLY after filesystem errors  When the filesystem is mounted with errors=remount-ro, we were setting SB_RDONLY flag to stop all filesystem modifications. We knew this misses proper locking (sb-\u0026gt;s_umount) and does not go through proper filesystem remount procedure but it has been the way this worked since early ext2 days and it was good enough for catastrophic situation damage mitigation. Recently, syzbot has found a way (see link) to trigger warnings in filesystem freezing because the code got confused by SB_RDONLY changing under its hands. Since these days we set EXT4_FLAGS_SHUTDOWN on the superblock which is enough to stop all filesystem modifications, modifying SB_RDONLY shouldn\u0026apos;t be needed. So stop doing that.(CVE-2024-50191)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  irqchip/gic-v4: Don\u0026apos;t allow a VMOVP on a dying VPE  Kunkun Jiang reported that there is a small window of opportunity for userspace to force a change of affinity for a VPE while the VPE has already been unmapped, but the corresponding doorbell interrupt still visible in /proc/irq/.  Plug the race by checking the value of vmapp_count, which tracks whether the VPE is mapped ot not, and returning an error in this case.  This involves making vmapp_count common to both GICv4.1 and its v4.0 ancestor.(CVE-2024-50192)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  posix-clock: Fix missing timespec64 check in pc_clock_settime()  As Andrew pointed out, it will make sense that the PTP core checked timespec64 struct\u0026apos;s tv_sec and tv_nsec range before calling ptp-\u0026gt;info-\u0026gt;settime64().  As the man manual of clock_settime() said, if tp.tv_sec is negative or tp.tv_nsec is outside the range [0..999,999,999], it should return EINVAL, which include dynamic clocks which handles PTP clock, and the condition is consistent with timespec64_valid(). As Thomas suggested, timespec64_valid() only check the timespec is valid, but not ensure that the time is in a valid range, so check it ahead using timespec64_valid_strict() in pc_clock_settime() and return -EINVAL if not valid.  There are some drivers that use tp-\u0026gt;tv_sec and tp-\u0026gt;tv_nsec directly to write registers without validity checks and assume that the higher layer has checked it, which is dangerous and will benefit from this, such as hclge_ptp_settime(), igb_ptp_settime_i210(), _rcar_gen4_ptp_settime(), and some drivers can remove the checks of itself.(CVE-2024-50195)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf, arm64: Fix address emission with tag-based KASAN enabled  When BPF_TRAMP_F_CALL_ORIG is enabled, the address of a bpf_tramp_image struct on the stack is passed during the size calculation pass and an address on the heap is passed during code generation. This may cause a heap buffer overflow if the heap address is tagged because emit_a64_mov_i64() will emit longer code than it did during the size calculation pass. The same problem could occur without tag-based KASAN if one of the 16-bit words of the stack address happened to be all-ones during the size calculation pass. Fix the problem by assuming the worst case (4 instructions) when calculating the size of the bpf_tramp_image address emission.(CVE-2024-50203)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ALSA: firewire-lib: Avoid division by zero in apply_constraint_to_size()  The step variable is initialized to zero. It is changed in the loop, but if it\u0026apos;s not changed it will remain zero. Add a variable check before the division.  The observed behavior was introduced by commit 826b5de90c0b (\u0026quot;ALSA: firewire-lib: fix insufficient PCM rule for period/buffer size\u0026quot;), and it is difficult to show that any of the interval parameters will satisfy the snd_interval_test() condition with data from the amdtp_rate_table[] table.  Found by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-50205)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/bnxt_re: Fix a bug while setting up Level-2 PBL pages  Avoid memory corruption while setting up Level-2 PBL pages for the non MR resources when num_pages \u0026gt; 256K.  There will be a single PDE page address (contiguous pages in the case of \u0026gt; PAGE_SIZE), but, current logic assumes multiple pages, leading to invalid memory access after 256K PBL entries in the PDE.(CVE-2024-50208)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/bnxt_re: Add a check for memory allocation  __alloc_pbl() can return error when memory allocation fails. Driver is not checking the status on one of the instances.(CVE-2024-50209)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  xfs: fix finding a last resort AG in xfs_filestream_pick_ag  When the main loop in xfs_filestream_pick_ag fails to find a suitable AG it tries to just pick the online AG.  But the loop for that uses args-\u0026gt;pag as loop iterator while the later code expects pag to be set.  Fix this by reusing the max_pag case for this last resort, and also add a check for impossible case of no AG just to make sure that the uninitialized pag doesn\u0026apos;t even escape in theory.(CVE-2024-50216)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: fix use-after-free of block device file in __btrfs_free_extra_devids()  Mounting btrfs from two images (which have the same one fsid and two different dev_uuids) in certain executing order may trigger an UAF for variable \u0026apos;device-\u0026gt;bdev_file\u0026apos; in __btrfs_free_extra_devids(). And following are the details:  1. Attach image_1 to loop0, attach image_2 to loop1, and scan btrfs    devices by ioctl(BTRFS_IOC_SCAN_DEV):               /  btrfs_device_1 \u2192 loop0    fs_device              \\  btrfs_device_2 \u2192 loop1 2. mount /dev/loop0 /mnt    btrfs_open_devices     btrfs_device_1-\u0026gt;bdev_file = btrfs_get_bdev_and_sb(loop0)     btrfs_device_2-\u0026gt;bdev_file = btrfs_get_bdev_and_sb(loop1)    btrfs_fill_super     open_ctree      fail: btrfs_close_devices // -ENOMEM      btrfs_close_bdev(btrfs_device_1)              fput(btrfs_device_1-\u0026gt;bdev_file)        // btrfs_device_1-\u0026gt;bdev_file is freed      btrfs_close_bdev(btrfs_device_2)              fput(btrfs_device_2-\u0026gt;bdev_file)  3. mount /dev/loop1 /mnt    btrfs_open_devices     btrfs_get_bdev_and_sb(\u0026amp;bdev_file)      // EIO, btrfs_device_1-\u0026gt;bdev_file is not assigned,      // which points to a freed memory area     btrfs_device_2-\u0026gt;bdev_file = btrfs_get_bdev_and_sb(loop1)    btrfs_fill_super     open_ctree      btrfs_free_extra_devids       if (btrfs_device_1-\u0026gt;bdev_file)        fput(btrfs_device_1-\u0026gt;bdev_file) // UAF !  Fix it by setting \u0026apos;device-\u0026gt;bdev_file\u0026apos; as \u0026apos;NULL\u0026apos; after closing the btrfs_device in btrfs_close_one_device().(CVE-2024-50217)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  sched/numa: Fix the potential null pointer dereference in task_numa_work()  When running stress-ng-vm-segv test, we found a null pointer dereference error in task_numa_work(). Here is the backtrace:    [323676.066985] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000020   ......   [323676.067108] CPU: 35 PID: 2694524 Comm: stress-ng-vm-se   ......   [323676.067113] pstate: 23401009 (nzCv daif +PAN -UAO +TCO +DIT +SSBS BTYPE=--)   [323676.067115] pc : vma_migratable+0x1c/0xd0   [323676.067122] lr : task_numa_work+0x1ec/0x4e0   [323676.067127] sp : ffff8000ada73d20   [323676.067128] x29: ffff8000ada73d20 x28: 0000000000000000 x27: 000000003e89f010   [323676.067130] x26: 0000000000080000 x25: ffff800081b5c0d8 x24: ffff800081b27000   [323676.067133] x23: 0000000000010000 x22: 0000000104d18cc0 x21: ffff0009f7158000   [323676.067135] x20: 0000000000000000 x19: 0000000000000000 x18: ffff8000ada73db8   [323676.067138] x17: 0001400000000000 x16: ffff800080df40b0 x15: 0000000000000035   [323676.067140] x14: ffff8000ada73cc8 x13: 1fffe0017cc72001 x12: ffff8000ada73cc8   [323676.067142] x11: ffff80008001160c x10: ffff000be639000c x9 : ffff8000800f4ba4   [323676.067145] x8 : ffff000810375000 x7 : ffff8000ada73974 x6 : 0000000000000001   [323676.067147] x5 : 0068000b33e26707 x4 : 0000000000000001 x3 : ffff0009f7158000   [323676.067149] x2 : 0000000000000041 x1 : 0000000000004400 x0 : 0000000000000000   [323676.067152] Call trace:   [323676.067153]  vma_migratable+0x1c/0xd0   [323676.067155]  task_numa_work+0x1ec/0x4e0   [323676.067157]  task_work_run+0x78/0xd8   [323676.067161]  do_notify_resume+0x1ec/0x290   [323676.067163]  el0_svc+0x150/0x160   [323676.067167]  el0t_64_sync_handler+0xf8/0x128   [323676.067170]  el0t_64_sync+0x17c/0x180   [323676.067173] Code: d2888001 910003fd f9000bf3 aa0003f3 (f9401000)   [323676.067177] SMP: stopping secondary CPUs   [323676.070184] Starting crashdump kernel...  stress-ng-vm-segv in stress-ng is used to stress test the SIGSEGV error handling function of the system, which tries to cause a SIGSEGV error on return from unmapping the whole address space of the child process.  Normally this program will not cause kernel crashes. But before the munmap system call returns to user mode, a potential task_numa_work() for numa balancing could be added and executed. In this scenario, since the child process has no vma after munmap, the vma_next() in task_numa_work() will return a null pointer even if the vma iterator restarts from 0.  Recheck the vma pointer before dereferencing it in task_numa_work().(CVE-2024-50223)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix kernel bug due to missing clearing of checked flag  Syzbot reported that in directory operations after nilfs2 detects filesystem corruption and degrades to read-only, __block_write_begin_int(), which is called to prepare block writes, may fail the BUG_ON check for accesses exceeding the folio/page size, triggering a kernel bug.  This was found to be because the \u0026quot;checked\u0026quot; flag of a page/folio was not cleared when it was discarded by nilfs2\u0026apos;s own routine, which causes the sanity check of directory entries to be skipped when the directory page/folio is reloaded.  So, fix that.  This was necessary when the use of nilfs2\u0026apos;s own page discard routine was applied to more than just metadata files.(CVE-2024-50230)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: iwlegacy: Clear stale interrupts before resuming device  iwl4965 fails upon resume from hibernation on my laptop. The reason seems to be a stale interrupt which isn\u0026apos;t being cleared out before interrupts are enabled. We end up with a race beween the resume trying to bring things back up, and the restart work (queued form the interrupt handler) trying to bring things down. Eventually the whole thing blows up.  Fix the problem by clearing out any stale interrupts before interrupts get enabled during resume.  Here\u0026apos;s a debug log of the indicent: [   12.042589] ieee80211 phy0: il_isr ISR inta 0x00000080, enabled 0xaa00008b, fh 0x00000000 [   12.042625] ieee80211 phy0: il4965_irq_tasklet inta 0x00000080, enabled 0x00000000, fh 0x00000000 [   12.042651] iwl4965 0000:10:00.0: RF_KILL bit toggled to enable radio. [   12.042653] iwl4965 0000:10:00.0: On demand firmware reload [   12.042690] ieee80211 phy0: il4965_irq_tasklet End inta 0x00000000, enabled 0xaa00008b, fh 0x00000000, flags 0x00000282 [   12.052207] ieee80211 phy0: il4965_mac_start enter [   12.052212] ieee80211 phy0: il_prep_station Add STA to driver ID 31: ff:ff:ff:ff:ff:ff [   12.052244] ieee80211 phy0: il4965_set_hw_ready hardware  ready [   12.052324] ieee80211 phy0: il_apm_init Init card\u0026apos;s basic functions [   12.052348] ieee80211 phy0: il_apm_init L1 Enabled; Disabling L0S [   12.055727] ieee80211 phy0: il4965_load_bsm Begin load bsm [   12.056140] ieee80211 phy0: il4965_verify_bsm Begin verify bsm [   12.058642] ieee80211 phy0: il4965_verify_bsm BSM bootstrap uCode image OK [   12.058721] ieee80211 phy0: il4965_load_bsm BSM write complete, poll 1 iterations [   12.058734] ieee80211 phy0: __il4965_up iwl4965 is coming up [   12.058737] ieee80211 phy0: il4965_mac_start Start UP work done. [   12.058757] ieee80211 phy0: __il4965_down iwl4965 is going down [   12.058761] ieee80211 phy0: il_scan_cancel_timeout Scan cancel timeout [   12.058762] ieee80211 phy0: il_do_scan_abort Not performing scan to abort [   12.058765] ieee80211 phy0: il_clear_ucode_stations Clearing ucode stations in driver [   12.058767] ieee80211 phy0: il_clear_ucode_stations No active stations found to be cleared [   12.058819] ieee80211 phy0: _il_apm_stop Stop card, put in low power state [   12.058827] ieee80211 phy0: _il_apm_stop_master stop master [   12.058864] ieee80211 phy0: il4965_clear_free_frames 0 frames on pre-allocated heap on clear. [   12.058869] ieee80211 phy0: Hardware restart was requested [   16.132299] iwl4965 0000:10:00.0: START_ALIVE timeout after 4000ms. [   16.132303] ------------[ cut here ]------------ [   16.132304] Hardware became unavailable upon resume. This could be a software issue prior to suspend or a hardware issue. [   16.132338] WARNING: CPU: 0 PID: 181 at net/mac80211/util.c:1826 ieee80211_reconfig+0x8f/0x14b0 [mac80211] [   16.132390] Modules linked in: ctr ccm sch_fq_codel xt_tcpudp xt_multiport xt_state iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv4 ip_tables x_tables binfmt_misc joydev mousedev btusb btrtl btintel btbcm bluetooth ecdh_generic ecc iTCO_wdt i2c_dev iwl4965 iwlegacy coretemp snd_hda_codec_analog pcspkr psmouse mac80211 snd_hda_codec_generic libarc4 sdhci_pci cqhci sha256_generic sdhci libsha256 firewire_ohci snd_hda_intel snd_intel_dspcfg mmc_core snd_hda_codec snd_hwdep firewire_core led_class iosf_mbi snd_hda_core uhci_hcd lpc_ich crc_itu_t cfg80211 ehci_pci ehci_hcd snd_pcm usbcore mfd_core rfkill snd_timer snd usb_common soundcore video parport_pc parport intel_agp wmi intel_gtt backlight e1000e agpgart evdev [   16.132456] CPU: 0 UID: 0 PID: 181 Comm: kworker/u8:6 Not tainted 6.11.0-cl+ #143 [   16.132460] Hardware name: Hewlett-Packard HP Compaq 6910p/30BE, BIOS 68MCU Ver. F.19 07/06/2010 [   16.132463] Workqueue: async async_run_entry_fn [   16.132469] RIP: 0010:ieee80211_reconfig+0x8f/0x14b0 [mac80211] [   16.132501] Code: da 02 00 0 ---truncated---(CVE-2024-50234)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: ath10k: Fix memory leak in management tx  In the current logic, memory is allocated for storing the MSDU context during management packet TX but this memory is not being freed during management TX completion. Similar leaks are seen in the management TX cleanup logic.  Kmemleak reports this problem as below,  unreferenced object 0xffffff80b64ed250 (size 16):   comm \u0026quot;kworker/u16:7\u0026quot;, pid 148, jiffies 4294687130 (age 714.199s)   hex dump (first 16 bytes):     00 2b d8 d8 80 ff ff ff c4 74 e9 fd 07 00 00 00  .+.......t......   backtrace:     [\u0026lt;ffffffe6e7b245dc\u0026gt;] __kmem_cache_alloc_node+0x1e4/0x2d8     [\u0026lt;ffffffe6e7adde88\u0026gt;] kmalloc_trace+0x48/0x110     [\u0026lt;ffffffe6bbd765fc\u0026gt;] ath10k_wmi_tlv_op_gen_mgmt_tx_send+0xd4/0x1d8 [ath10k_core]     [\u0026lt;ffffffe6bbd3eed4\u0026gt;] ath10k_mgmt_over_wmi_tx_work+0x134/0x298 [ath10k_core]     [\u0026lt;ffffffe6e78d5974\u0026gt;] process_scheduled_works+0x1ac/0x400     [\u0026lt;ffffffe6e78d60b8\u0026gt;] worker_thread+0x208/0x328     [\u0026lt;ffffffe6e78dc890\u0026gt;] kthread+0x100/0x1c0     [\u0026lt;ffffffe6e78166c0\u0026gt;] ret_from_fork+0x10/0x20  Free the memory during completion and cleanup to fix the leak.  Protect the mgmt_pending_tx idr_remove() operation in ath10k_wmi_tlv_op_cleanup_mgmt_tx_send() using ar-\u0026gt;data_lock similar to other instances.  Tested-on: WCN3990 hw1.0 SNOC WLAN.HL.2.0-01387-QCAHLSWMTPLZ-1(CVE-2024-50236)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  NFSD: Initialize struct nfsd4_copy earlier  Ensure the refcount and async_copies fields are initialized early. cleanup_async_copy() will reference these fields if an error occurs in nfsd4_copy(). If they are not correctly initialized, at the very least, a refcount underflow occurs.(CVE-2024-50241)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ntfs3: Add bounds checking to mi_enum_attr()  Added bounds checking to make sure that every attr don\u0026apos;t stray beyond valid memory region.(CVE-2024-50248)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  Bluetooth: hci: fix null-ptr-deref in hci_read_supported_codecs  Fix __hci_cmd_sync_sk() to return not NULL for unknown opcodes.  __hci_cmd_sync_sk() returns NULL if a command returns a status event. However, it also returns NULL where an opcode doesn\u0026apos;t exist in the hci_cc table because hci_cmd_complete_evt() assumes status = skb-\u0026gt;data[0] for unknown opcodes. This leads to null-ptr-deref in cmd_sync for HCI_OP_READ_LOCAL_CODECS as there is no hci_cc for HCI_OP_READ_LOCAL_CODECS, which always assumes status = skb-\u0026gt;data[0].  KASAN: null-ptr-deref in range [0x0000000000000070-0x0000000000000077] CPU: 1 PID: 2000 Comm: kworker/u9:5 Not tainted 6.9.0-ga6bcb805883c-dirty #10 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Workqueue: hci7 hci_power_on RIP: 0010:hci_read_supported_codecs+0xb9/0x870 net/bluetooth/hci_codec.c:138 Code: 08 48 89 ef e8 b8 c1 8f fd 48 8b 75 00 e9 96 00 00 00 49 89 c6 48 ba 00 00 00 00 00 fc ff df 4c 8d 60 70 4c 89 e3 48 c1 eb 03 \u0026lt;0f\u0026gt; b6 04 13 84 c0 0f 85 82 06 00 00 41 83 3c 24 02 77 0a e8 bf 78 RSP: 0018:ffff888120bafac8 EFLAGS: 00010212 RAX: 0000000000000000 RBX: 000000000000000e RCX: ffff8881173f0040 RDX: dffffc0000000000 RSI: ffffffffa58496c0 RDI: ffff88810b9ad1e4 RBP: ffff88810b9ac000 R08: ffffffffa77882a7 R09: 1ffffffff4ef1054 R10: dffffc0000000000 R11: fffffbfff4ef1055 R12: 0000000000000070 R13: 0000000000000000 R14: 0000000000000000 R15: ffff88810b9ac000 FS:  0000000000000000(0000) GS:ffff8881f6c00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f6ddaa3439e CR3: 0000000139764003 CR4: 0000000000770ef0 PKRU: 55555554 Call Trace:  \u0026lt;TASK\u0026gt;  hci_read_local_codecs_sync net/bluetooth/hci_sync.c:4546 [inline]  hci_init_stage_sync net/bluetooth/hci_sync.c:3441 [inline]  hci_init4_sync net/bluetooth/hci_sync.c:4706 [inline]  hci_init_sync net/bluetooth/hci_sync.c:4742 [inline]  hci_dev_init_sync net/bluetooth/hci_sync.c:4912 [inline]  hci_dev_open_sync+0x19a9/0x2d30 net/bluetooth/hci_sync.c:4994  hci_dev_do_open net/bluetooth/hci_core.c:483 [inline]  hci_power_on+0x11e/0x560 net/bluetooth/hci_core.c:1015  process_one_work kernel/workqueue.c:3267 [inline]  process_scheduled_works+0x8ef/0x14f0 kernel/workqueue.c:3348  worker_thread+0x91f/0xe50 kernel/workqueue.c:3429  kthread+0x2cb/0x360 kernel/kthread.c:388  ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-50255)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: fix crash when config small gso_max_size/gso_ipv4_max_size  Config a small gso_max_size/gso_ipv4_max_size will lead to an underflow in sk_dst_gso_max_size(), which may trigger a BUG_ON crash, because sk-\u0026gt;sk_gso_max_size would be much bigger than device limits. Call Trace: tcp_write_xmit     tso_segs = tcp_init_tso_segs(skb, mss_now);         tcp_set_skb_tso_segs             tcp_skb_pcount_set                 // skb-\u0026gt;len = 524288, mss_now = 8                 // u16 tso_segs = 524288/8 = 65535 -\u0026gt; 0                 tso_segs = DIV_ROUND_UP(skb-\u0026gt;len, mss_now)     BUG_ON(!tso_segs) Add check for the minimum value of gso_max_size and gso_ipv4_max_size.(CVE-2024-50258)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf: Fix out-of-bounds write in trie_get_next_key()  trie_get_next_key() allocates a node stack with size trie-\u0026gt;max_prefixlen, while it writes (trie-\u0026gt;max_prefixlen + 1) nodes to the stack when it has full paths from the root to leaves. For example, consider a trie with max_prefixlen is 8, and the nodes with key 0x00/0, 0x00/1, 0x00/2, ... 0x00/8 inserted. Subsequent calls to trie_get_next_key with _key with .prefixlen = 8 make 9 nodes be written on the node stack with size 8.(CVE-2024-50262)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: remove entry once instead of null-ptr-dereference in ocfs2_xa_remove()  Syzkaller is able to provoke null-ptr-dereference in ocfs2_xa_remove():  [   57.319872] (a.out,1161,7):ocfs2_xa_remove:2028 ERROR: status = -12 [   57.320420] (a.out,1161,7):ocfs2_xa_cleanup_value_truncate:1999 ERROR: Partial truncate while removing xattr overlay.upper.  Leaking 1 clusters and removing the entry [   57.321727] BUG: kernel NULL pointer dereference, address: 0000000000000004 [...] [   57.325727] RIP: 0010:ocfs2_xa_block_wipe_namevalue+0x2a/0xc0 [...] [   57.331328] Call Trace: [   57.331477]  \u0026lt;TASK\u0026gt; [...] [   57.333511]  ? do_user_addr_fault+0x3e5/0x740 [   57.333778]  ? exc_page_fault+0x70/0x170 [   57.334016]  ? asm_exc_page_fault+0x2b/0x30 [   57.334263]  ? __pfx_ocfs2_xa_block_wipe_namevalue+0x10/0x10 [   57.334596]  ? ocfs2_xa_block_wipe_namevalue+0x2a/0xc0 [   57.334913]  ocfs2_xa_remove_entry+0x23/0xc0 [   57.335164]  ocfs2_xa_set+0x704/0xcf0 [   57.335381]  ? _raw_spin_unlock+0x1a/0x40 [   57.335620]  ? ocfs2_inode_cache_unlock+0x16/0x20 [   57.335915]  ? trace_preempt_on+0x1e/0x70 [   57.336153]  ? start_this_handle+0x16c/0x500 [   57.336410]  ? preempt_count_sub+0x50/0x80 [   57.336656]  ? _raw_read_unlock+0x20/0x40 [   57.336906]  ? start_this_handle+0x16c/0x500 [   57.337162]  ocfs2_xattr_block_set+0xa6/0x1e0 [   57.337424]  __ocfs2_xattr_set_handle+0x1fd/0x5d0 [   57.337706]  ? ocfs2_start_trans+0x13d/0x290 [   57.337971]  ocfs2_xattr_set+0xb13/0xfb0 [   57.338207]  ? dput+0x46/0x1c0 [   57.338393]  ocfs2_xattr_trusted_set+0x28/0x30 [   57.338665]  ? ocfs2_xattr_trusted_set+0x28/0x30 [   57.338948]  __vfs_removexattr+0x92/0xc0 [   57.339182]  __vfs_removexattr_locked+0xd5/0x190 [   57.339456]  ? preempt_count_sub+0x50/0x80 [   57.339705]  vfs_removexattr+0x5f/0x100 [...]  Reproducer uses faultinject facility to fail ocfs2_xa_remove() -\u0026gt; ocfs2_xa_value_truncate() with -ENOMEM.  In this case the comment mentions that we can return 0 if ocfs2_xa_cleanup_value_truncate() is going to wipe the entry anyway. But the following \u0026apos;rc\u0026apos; check is wrong and execution flow do \u0026apos;ocfs2_xa_remove_entry(loc);\u0026apos; twice: * 1st: in ocfs2_xa_cleanup_value_truncate(); * 2nd: returning back to ocfs2_xa_remove() instead of going to \u0026apos;out\u0026apos;.  Fix this by skipping the 2nd removal of the same entry and making syzkaller repro happy.(CVE-2024-50265)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  usb: musb: sunxi: Fix accessing an released usb phy  Commit 6ed05c68cbca (\u0026quot;usb: musb: sunxi: Explicitly release USB PHY on exit\u0026quot;) will cause that usb phy @glue-\u0026gt;xceiv is accessed after released.  1) register platform driver @sunxi_musb_driver // get the usb phy @glue-\u0026gt;xceiv sunxi_musb_probe() -\u0026gt; devm_usb_get_phy().  2) register and unregister platform driver @musb_driver musb_probe() -\u0026gt; sunxi_musb_init() use the phy here //the phy is released here musb_remove() -\u0026gt; sunxi_musb_exit() -\u0026gt; devm_usb_put_phy()  3) register @musb_driver again musb_probe() -\u0026gt; sunxi_musb_init() use the phy here but the phy has been released at 2). ...  Fixed by reverting the commit, namely, removing devm_usb_put_phy() from sunxi_musb_exit().(CVE-2024-50269)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  signal: restore the override_rlimit logic  Prior to commit d64696905554 (\u0026quot;Reimplement RLIMIT_SIGPENDING on top of ucounts\u0026quot;) UCOUNT_RLIMIT_SIGPENDING rlimit was not enforced for a class of signals.  However now it\u0026apos;s enforced unconditionally, even if override_rlimit is set.  This behavior change caused production issues.    For example, if the limit is reached and a process receives a SIGSEGV signal, sigqueue_alloc fails to allocate the necessary resources for the signal delivery, preventing the signal from being delivered with siginfo.  This prevents the process from correctly identifying the fault address and handling the error.  From the user-space perspective, applications are unaware that the limit has been reached and that the siginfo is effectively \u0026apos;corrupted\u0026apos;.  This can lead to unpredictable behavior and crashes, as we observed with java applications.  Fix this by passing override_rlimit into inc_rlimit_get_ucounts() and skip the comparison to max there if override_rlimit is set.  This effectively restores the old behavior.(CVE-2024-50271)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  filemap: Fix bounds checking in filemap_read()  If the caller supplies an iocb-\u0026gt;ki_pos value that is close to the filesystem upper limit, and an iterator with a count that causes us to overflow that limit, then filemap_read() enters an infinite loop.  This behaviour was discovered when testing xfstests generic/525 with the \u0026quot;localio\u0026quot; optimisation for loopback NFS mounts.(CVE-2024-50272)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: reinitialize delayed ref list after deleting it from the list  At insert_delayed_ref() if we need to update the action of an existing ref to BTRFS_DROP_DELAYED_REF, we delete the ref from its ref head\u0026apos;s ref_add_list using list_del(), which leaves the ref\u0026apos;s add_list member not reinitialized, as list_del() sets the next and prev members of the list to LIST_POISON1 and LIST_POISON2, respectively.  If later we end up calling drop_delayed_ref() against the ref, which can happen during merging or when destroying delayed refs due to a transaction abort, we can trigger a crash since at drop_delayed_ref() we call list_empty() against the ref\u0026apos;s add_list, which returns false since the list was not reinitialized after the list_del() and as a consequence we call list_del() again at drop_delayed_ref(). This results in an invalid list access since the next and prev members are set to poison pointers, resulting in a splat if CONFIG_LIST_HARDENED and CONFIG_DEBUG_LIST are set or invalid poison pointer dereferences otherwise.  So fix this by deleting from the list with list_del_init() instead.(CVE-2024-50273)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  arm64/sve: Discard stale CPU state when handling SVE traps  The logic for handling SVE traps manipulates saved FPSIMD/SVE state incorrectly, and a race with preemption can result in a task having TIF_SVE set and TIF_FOREIGN_FPSTATE clear even though the live CPU state is stale (e.g. with SVE traps enabled). This has been observed to result in warnings from do_sve_acc() where SVE traps are not expected while TIF_SVE is set:  |         if (test_and_set_thread_flag(TIF_SVE)) |                 WARN_ON(1); /* SVE access shouldn\u0026apos;t have trapped */  Warnings of this form have been reported intermittently, e.g.    https://lore.kernel.org/linux-arm-kernel/CA+G9fYtEGe_DhY2Ms7+L7NKsLYUomGsgqpdBj+QwDLeSg=JhGg@mail.gmail.com/   https://lore.kernel.org/linux-arm-kernel/000000000000511e9a060ce5a45c@google.com/  The race can occur when the SVE trap handler is preempted before and after manipulating the saved FPSIMD/SVE state, starting and ending on the same CPU, e.g.  | void do_sve_acc(unsigned long esr, struct pt_regs *regs) | { |         // Trap on CPU 0 with TIF_SVE clear, SVE traps enabled |         // task-\u0026gt;fpsimd_cpu is 0. |         // per_cpu_ptr(\u0026amp;fpsimd_last_state, 0) is task. | |         ... | |         // Preempted; migrated from CPU 0 to CPU 1. |         // TIF_FOREIGN_FPSTATE is set. | |         get_cpu_fpsimd_context(); | |         if (test_and_set_thread_flag(TIF_SVE)) |                 WARN_ON(1); /* SVE access shouldn\u0026apos;t have trapped */ | |         sve_init_regs() { |                 if (!test_thread_flag(TIF_FOREIGN_FPSTATE)) { |                         ... |                 } else { |                         fpsimd_to_sve(current); |                         current-\u0026gt;thread.fp_type = FP_STATE_SVE; |                 } |         } | |         put_cpu_fpsimd_context(); | |         // Preempted; migrated from CPU 1 to CPU 0. |         // task-\u0026gt;fpsimd_cpu is still 0 |         // If per_cpu_ptr(\u0026amp;fpsimd_last_state, 0) is still task then: |         // - Stale HW state is reused (with SVE traps enabled) |         // - TIF_FOREIGN_FPSTATE is cleared |         // - A return to userspace skips HW state restore | }  Fix the case where the state is not live and TIF_FOREIGN_FPSTATE is set by calling fpsimd_flush_task_state() to detach from the saved CPU state. This ensures that a subsequent context switch will not reuse the stale CPU state, and will instead set TIF_FOREIGN_FPSTATE, forcing the new state to be reloaded from memory prior to a return to userspace.(CVE-2024-50275)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: vertexcom: mse102x: Fix possible double free of TX skb  The scope of the TX skb is wider than just mse102x_tx_frame_spi(), so in case the TX skb room needs to be expanded, we should free the the temporary skb instead of the original skb. Otherwise the original TX skb pointer would be freed again in mse102x_tx_work(), which leads to crashes:    Internal error: Oops: 0000000096000004 [#2] PREEMPT SMP   CPU: 0 PID: 712 Comm: kworker/0:1 Tainted: G      D            6.6.23   Hardware name: chargebyte Charge SOM DC-ONE (DT)   Workqueue: events mse102x_tx_work [mse102x]   pstate: 20400009 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)   pc : skb_release_data+0xb8/0x1d8   lr : skb_release_data+0x1ac/0x1d8   sp : ffff8000819a3cc0   x29: ffff8000819a3cc0 x28: ffff0000046daa60 x27: ffff0000057f2dc0   x26: ffff000005386c00 x25: 0000000000000002 x24: 00000000ffffffff   x23: 0000000000000000 x22: 0000000000000001 x21: ffff0000057f2e50   x20: 0000000000000006 x19: 0000000000000000 x18: ffff00003fdacfcc   x17: e69ad452d0c49def x16: 84a005feff870102 x15: 0000000000000000   x14: 000000000000024a x13: 0000000000000002 x12: 0000000000000000   x11: 0000000000000400 x10: 0000000000000930 x9 : ffff00003fd913e8   x8 : fffffc00001bc008   x7 : 0000000000000000 x6 : 0000000000000008   x5 : ffff00003fd91340 x4 : 0000000000000000 x3 : 0000000000000009   x2 : 00000000fffffffe x1 : 0000000000000000 x0 : 0000000000000000   Call trace:    skb_release_data+0xb8/0x1d8    kfree_skb_reason+0x48/0xb0    mse102x_tx_work+0x164/0x35c [mse102x]    process_one_work+0x138/0x260    worker_thread+0x32c/0x438    kthread+0x118/0x11c    ret_from_fork+0x10/0x20   Code: aa1303e0 97fffab6 72001c1f 54000141 (f9400660)(CVE-2024-50276)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ksmbd: fix slab-use-after-free in smb3_preauth_hash_rsp  ksmbd_user_session_put should be called under smb3_preauth_hash_rsp(). It will avoid freeing session before calling smb3_preauth_hash_rsp().(CVE-2024-50283)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ksmbd: Fix the missing xa_store error check  xa_store() can fail, it return xa_err(-EINVAL) if the entry cannot be stored in an XArray, or xa_err(-ENOMEM) if memory allocation failed, so check error for xa_store() to fix it.(CVE-2024-50284)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: av7110: fix a spectre vulnerability  As warned by smatch:  drivers/staging/media/av7110/av7110_ca.c:270 dvb_ca_ioctl() warn: potential spectre issue \u0026apos;av7110-\u0026gt;ci_slot\u0026apos; [w] (local cap)  There is a spectre-related vulnerability at the code. Fix it.(CVE-2024-50289)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  rxrpc: Fix missing locking causing hanging calls  If a call gets aborted (e.g. because kafs saw a signal) between it being queued for connection and the I/O thread picking up the call, the abort will be prioritised over the connection and it will be removed from local-\u0026gt;new_client_calls by rxrpc_disconnect_client_call() without a lock being held.  This may cause other calls on the list to disappear if a race occurs.  Fix this by taking the client_call_lock when removing a call from whatever list its -\u0026gt;wait_link happens to be on.(CVE-2024-50294)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: enetc: allocate vf_state during PF probes  In the previous implementation, vf_state is allocated memory only when VF is enabled. However, net_device_ops::ndo_set_vf_mac() may be called before VF is enabled to configure the MAC address of VF. If this is the case, enetc_pf_set_vf_mac() will access vf_state, resulting in access to a null pointer. The simplified error log is as follows.  root@ls1028ardb:~# ip link set eno0 vf 1 mac 00:0c:e7:66:77:89 [  173.543315] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000004 [  173.637254] pc : enetc_pf_set_vf_mac+0x3c/0x80 Message from sy [  173.641973] lr : do_setlink+0x4a8/0xec8 [  173.732292] Call trace: [  173.734740]  enetc_pf_set_vf_mac+0x3c/0x80 [  173.738847]  __rtnl_newlink+0x530/0x89c [  173.742692]  rtnl_newlink+0x50/0x7c [  173.746189]  rtnetlink_rcv_msg+0x128/0x390 [  173.750298]  netlink_rcv_skb+0x60/0x130 [  173.754145]  rtnetlink_rcv+0x18/0x24 [  173.757731]  netlink_unicast+0x318/0x380 [  173.761665]  netlink_sendmsg+0x17c/0x3c8(CVE-2024-50298)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  sctp: properly validate chunk size in sctp_sf_ootb()  A size validation fix similar to that in Commit 50619dbf8db7 (\u0026quot;sctp: add size validation when walking chunks\u0026quot;) is also required in sctp_sf_ootb() to address a crash reported by syzbot:    BUG: KMSAN: uninit-value in sctp_sf_ootb+0x7f5/0xce0 net/sctp/sm_statefuns.c:3712   sctp_sf_ootb+0x7f5/0xce0 net/sctp/sm_statefuns.c:3712   sctp_do_sm+0x181/0x93d0 net/sctp/sm_sideeffect.c:1166   sctp_endpoint_bh_rcv+0xc38/0xf90 net/sctp/endpointola.c:407   sctp_inq_push+0x2ef/0x380 net/sctp/inqueue.c:88   sctp_rcv+0x3831/0x3b20 net/sctp/input.c:243   sctp4_rcv+0x42/0x50 net/sctp/protocol.c:1159   ip_protocol_deliver_rcu+0xb51/0x13d0 net/ipv4/ip_input.c:205   ip_local_deliver_finish+0x336/0x500 net/ipv4/ip_input.c:233(CVE-2024-50299)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  mctp i2c: handle NULL header address  daddr can be NULL if there is no neighbour table entry present, in that case the tx packet should be dropped.  saddr will usually be set by MCTP core, but check for NULL in case a packet is transmitted by a different protocol.(CVE-2024-53043)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  arm64: dts: imx8ulp: correct the flexspi compatible string  The flexspi on imx8ulp only has 16 LUTs, and imx8mm flexspi has 32 LUTs, so correct the compatible string here, otherwise will meet below error:  [    1.119072] ------------[ cut here ]------------ [    1.123926] WARNING: CPU: 0 PID: 1 at drivers/spi/spi-nxp-fspi.c:855 nxp_fspi_exec_op+0xb04/0xb64 [    1.133239] Modules linked in: [    1.136448] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.11.0-rc6-next-20240902-00001-g131bf9439dd9 #69 [    1.146821] Hardware name: NXP i.MX8ULP EVK (DT) [    1.151647] pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [    1.158931] pc : nxp_fspi_exec_op+0xb04/0xb64 [    1.163496] lr : nxp_fspi_exec_op+0xa34/0xb64 [    1.168060] sp : ffff80008002b2a0 [    1.171526] x29: ffff80008002b2d0 x28: 0000000000000000 x27: 0000000000000000 [    1.179002] x26: ffff2eb645542580 x25: ffff800080610014 x24: ffff800080610000 [    1.186480] x23: ffff2eb645548080 x22: 0000000000000006 x21: ffff2eb6455425e0 [    1.193956] x20: 0000000000000000 x19: ffff80008002b5e0 x18: ffffffffffffffff [    1.201432] x17: ffff2eb644467508 x16: 0000000000000138 x15: 0000000000000002 [    1.208907] x14: 0000000000000000 x13: ffff2eb6400d8080 x12: 00000000ffffff00 [    1.216378] x11: 0000000000000000 x10: ffff2eb6400d8080 x9 : ffff2eb697adca80 [    1.223850] x8 : ffff2eb697ad3cc0 x7 : 0000000100000000 x6 : 0000000000000001 [    1.231324] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 00000000000007a6 [    1.238795] x2 : 0000000000000000 x1 : 00000000000001ce x0 : 00000000ffffff92 [    1.246267] Call trace: [    1.248824]  nxp_fspi_exec_op+0xb04/0xb64 [    1.253031]  spi_mem_exec_op+0x3a0/0x430 [    1.257139]  spi_nor_read_id+0x80/0xcc [    1.261065]  spi_nor_scan+0x1ec/0xf10 [    1.264901]  spi_nor_probe+0x108/0x2fc [    1.268828]  spi_mem_probe+0x6c/0xbc [    1.272574]  spi_probe+0x84/0xe4 [    1.275958]  really_probe+0xbc/0x29c [    1.279713]  __driver_probe_device+0x78/0x12c [    1.284277]  driver_probe_device+0xd8/0x15c [    1.288660]  __device_attach_driver+0xb8/0x134 [    1.293316]  bus_for_each_drv+0x88/0xe8 [    1.297337]  __device_attach+0xa0/0x190 [    1.301353]  device_initial_probe+0x14/0x20 [    1.305734]  bus_probe_device+0xac/0xb0 [    1.309752]  device_add+0x5d0/0x790 [    1.313408]  __spi_add_device+0x134/0x204 [    1.317606]  of_register_spi_device+0x3b4/0x590 [    1.322348]  spi_register_controller+0x47c/0x754 [    1.327181]  devm_spi_register_controller+0x4c/0xa4 [    1.332289]  nxp_fspi_probe+0x1cc/0x2b0 [    1.336307]  platform_probe+0x68/0xc4 [    1.340145]  really_probe+0xbc/0x29c [    1.343893]  __driver_probe_device+0x78/0x12c [    1.348457]  driver_probe_device+0xd8/0x15c [    1.352838]  __driver_attach+0x90/0x19c [    1.356857]  bus_for_each_dev+0x7c/0xdc [    1.360877]  driver_attach+0x24/0x30 [    1.364624]  bus_add_driver+0xe4/0x208 [    1.368552]  driver_register+0x5c/0x124 [    1.372573]  __platform_driver_register+0x28/0x34 [    1.377497]  nxp_fspi_driver_init+0x1c/0x28 [    1.381888]  do_one_initcall+0x80/0x1c8 [    1.385908]  kernel_init_freeable+0x1c4/0x28c [    1.390472]  kernel_init+0x20/0x1d8 [    1.394138]  ret_from_fork+0x10/0x20 [    1.397885] ---[ end trace 0000000000000000 ]--- [    1.407908] ------------[ cut here ]------------(CVE-2024-53046)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  mptcp: init: protect sched with rcu_read_lock  Enabling CONFIG_PROVE_RCU_LIST with its dependence CONFIG_RCU_EXPERT creates this splat when an MPTCP socket is created:    =============================   WARNING: suspicious RCU usage   6.12.0-rc2+ #11 Not tainted   -----------------------------   net/mptcp/sched.c:44 RCU-list traversed in non-reader section!!    other info that might help us debug this:    rcu_scheduler_active = 2, debug_locks = 1   no locks held by mptcp_connect/176.    stack backtrace:   CPU: 0 UID: 0 PID: 176 Comm: mptcp_connect Not tainted 6.12.0-rc2+ #11   Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011   Call Trace:    \u0026lt;TASK\u0026gt;    dump_stack_lvl (lib/dump_stack.c:123)    lockdep_rcu_suspicious (kernel/locking/lockdep.c:6822)    mptcp_sched_find (net/mptcp/sched.c:44 (discriminator 7))    mptcp_init_sock (net/mptcp/protocol.c:2867 (discriminator 1))    ? sock_init_data_uid (arch/x86/include/asm/atomic.h:28)    inet_create.part.0.constprop.0 (net/ipv4/af_inet.c:386)    ? __sock_create (include/linux/rcupdate.h:347 (discriminator 1))    __sock_create (net/socket.c:1576)    __sys_socket (net/socket.c:1671)    ? __pfx___sys_socket (net/socket.c:1712)    ? do_user_addr_fault (arch/x86/mm/fault.c:1419 (discriminator 1))    __x64_sys_socket (net/socket.c:1728)    do_syscall_64 (arch/x86/entry/common.c:52 (discriminator 1))    entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)  That\u0026apos;s because when the socket is initialised, rcu_read_lock() is not used despite the explicit comment written above the declaration of mptcp_sched_find() in sched.c. Adding the missing lock/unlock avoids the warning.(CVE-2024-53047)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  io_uring/rw: fix missing NOWAIT check for O_DIRECT start write  When io_uring starts a write, it\u0026apos;ll call kiocb_start_write() to bump the super block rwsem, preventing any freezes from happening while that write is in-flight. The freeze side will grab that rwsem for writing, excluding any new writers from happening and waiting for existing writes to finish. But io_uring unconditionally uses kiocb_start_write(), which will block if someone is currently attempting to freeze the mount point. This causes a deadlock where freeze is waiting for previous writes to complete, but the previous writes cannot complete, as the task that is supposed to complete them is blocked waiting on starting a new write. This results in the following stuck trace showing that dependency with the write blocked starting a new write:  task:fio             state:D stack:0     pid:886   tgid:886   ppid:876 Call trace:  __switch_to+0x1d8/0x348  __schedule+0x8e8/0x2248  schedule+0x110/0x3f0  percpu_rwsem_wait+0x1e8/0x3f8  __percpu_down_read+0xe8/0x500  io_write+0xbb8/0xff8  io_issue_sqe+0x10c/0x1020  io_submit_sqes+0x614/0x2110  __arm64_sys_io_uring_enter+0x524/0x1038  invoke_syscall+0x74/0x268  el0_svc_common.constprop.0+0x160/0x238  do_el0_svc+0x44/0x60  el0_svc+0x44/0xb0  el0t_64_sync_handler+0x118/0x128  el0t_64_sync+0x168/0x170 INFO: task fsfreeze:7364 blocked for more than 15 seconds.       Not tainted 6.12.0-rc5-00063-g76aaf945701c #7963  with the attempting freezer stuck trying to grab the rwsem:  task:fsfreeze        state:D stack:0     pid:7364  tgid:7364  ppid:995 Call trace:  __switch_to+0x1d8/0x348  __schedule+0x8e8/0x2248  schedule+0x110/0x3f0  percpu_down_write+0x2b0/0x680  freeze_super+0x248/0x8a8  do_vfs_ioctl+0x149c/0x1b18  __arm64_sys_ioctl+0xd0/0x1a0  invoke_syscall+0x74/0x268  el0_svc_common.constprop.0+0x160/0x238  do_el0_svc+0x44/0x60  el0_svc+0x44/0xb0  el0t_64_sync_handler+0x118/0x128  el0t_64_sync+0x168/0x170  Fix this by having the io_uring side honor IOCB_NOWAIT, and only attempt a blocking grab of the super block rwsem if it isn\u0026apos;t set. For normal issue where IOCB_NOWAIT would always be set, this returns -EAGAIN which will have io_uring core issue a blocking attempt of the write. That will in turn also get completions run, ensuring forward progress.  Since freezing requires CAP_SYS_ADMIN in the first place, this isn\u0026apos;t something that can be triggered by a regular user.(CVE-2024-53052)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: iwlwifi: mvm: fix 6 GHz scan construction  If more than 255 colocated APs exist for the set of all APs found during 2.4/5 GHz scanning, then the 6 GHz scan construction will loop forever since the loop variable has type u8, which can never reach the number found when that\u0026apos;s bigger than 255, and is stored in a u32 variable. Also move it into the loops to have a smaller scope.  Using a u32 there is fine, we limit the number of APs in the scan list and each has a limit on the number of RNR entries due to the frame size. With a limit of 1000 scan results, a frame size upper bound of 4096 (really it\u0026apos;s more like ~2300) and a TBTT entry size of at least 11, we get an upper bound for the number of ~372k, well in the bounds of a u32.(CVE-2024-53055)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: s5p-jpeg: prevent buffer overflows  The current logic allows word to be less than 2. If this happens, there will be buffer overflows, as reported by smatch. Add extra checks to prevent it.  While here, remove an unused word = 0 assignment.(CVE-2024-53061)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: dvbdev: prevent the risk of out of memory access  The dvbdev contains a static variable used to store dvb minors.  The behavior of it depends if CONFIG_DVB_DYNAMIC_MINORS is set or not. When not set, dvb_register_device() won\u0026apos;t check for boundaries, as it will rely that a previous call to dvb_register_adapter() would already be enforcing it.  On a similar way, dvb_device_open() uses the assumption that the register functions already did the needed checks.  This can be fragile if some device ends using different calls. This also generate warnings on static check analysers like Coverity.  So, add explicit guards to prevent potential risk of OOM issues.(CVE-2024-53063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfs: Fix KMSAN warning in decode_getfattr_attrs()  Fix the following KMSAN warning:  CPU: 1 UID: 0 PID: 7651 Comm: cp Tainted: G    B Tainted: [B]=BAD_PAGE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009) ===================================================== ===================================================== BUG: KMSAN: uninit-value in decode_getfattr_attrs+0x2d6d/0x2f90  decode_getfattr_attrs+0x2d6d/0x2f90  decode_getfattr_generic+0x806/0xb00  nfs4_xdr_dec_getattr+0x1de/0x240  rpcauth_unwrap_resp_decode+0xab/0x100  rpcauth_unwrap_resp+0x95/0xc0  call_decode+0x4ff/0xb50  __rpc_execute+0x57b/0x19d0  rpc_execute+0x368/0x5e0  rpc_run_task+0xcfe/0xee0  nfs4_proc_getattr+0x5b5/0x990  __nfs_revalidate_inode+0x477/0xd00  nfs_access_get_cached+0x1021/0x1cc0  nfs_do_access+0x9f/0xae0  nfs_permission+0x1e4/0x8c0  inode_permission+0x356/0x6c0  link_path_walk+0x958/0x1330  path_lookupat+0xce/0x6b0  filename_lookup+0x23e/0x770  vfs_statx+0xe7/0x970  vfs_fstatat+0x1f2/0x2c0  __se_sys_newfstatat+0x67/0x880  __x64_sys_newfstatat+0xbd/0x120  x64_sys_call+0x1826/0x3cf0  do_syscall_64+0xd0/0x1b0  entry_SYSCALL_64_after_hwframe+0x77/0x7f  The KMSAN warning is triggered in decode_getfattr_attrs(), when calling decode_attr_mdsthreshold(). It appears that fattr-\u0026gt;mdsthreshold is not initialized.  Fix the issue by initializing fattr-\u0026gt;mdsthreshold to NULL in nfs_fattr_init().(CVE-2024-53066)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  iio: gts-helper: Fix memory leaks for the error path of iio_gts_build_avail_scale_table()  If per_time_scales[i] or per_time_gains[i] kcalloc fails in the for loop of iio_gts_build_avail_scale_table(), the err_free_out will fail to call kfree() each time when i is reduced to 0, so all the per_time_scales[0] and per_time_gains[0] will not be freed, which will cause memory leaks.  Fix it by checking if i \u0026gt;= 0.(CVE-2024-53076)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  usb: typec: qcom-pmic: init value of hdr_len/txbuf_len earlier  If the read of USB_PDPHY_RX_ACKNOWLEDGE_REG failed, then hdr_len and txbuf_len are uninitialized. This commit stops to print uninitialized value and misleading/false data.(CVE-2024-53083)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tpm: Lock TPM chip in tpm_pm_suspend() first  Setting TPM_CHIP_FLAG_SUSPENDED in the end of tpm_pm_suspend() can be racy according, as this leaves window for tpm_hwrng_read() to be called while the operation is in progress. The recent bug report gives also evidence of this behaviour.  Aadress this by locking the TPM chip before checking any chip-\u0026gt;flags both in tpm_pm_suspend() and tpm_hwrng_read(). Move TPM_CHIP_FLAG_SUSPENDED check inside tpm_get_random() so that it will be always checked only when the lock is reserved.(CVE-2024-53085)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  LoongArch: KVM: Mark hrtimer to expire in hard interrupt context  Like commit 2c0d278f3293f (\u0026quot;KVM: LAPIC: Mark hrtimer to expire in hard interrupt context\u0026quot;) and commit 9090825fa9974 (\u0026quot;KVM: arm/arm64: Let the timer expire in hardirq context on RT\u0026quot;), On PREEMPT_RT enabled kernels unmarked hrtimers are moved into soft interrupt expiry mode by default. Then the timers are canceled from an preempt-notifier which is invoked with disabled preemption which is not allowed on PREEMPT_RT.  The timer callback is short so in could be invoked in hard-IRQ context. So let the timer expire on hard-IRQ context even on -RT.  This fix a \u0026quot;scheduling while atomic\u0026quot; bug for PREEMPT_RT enabled kernels:   BUG: scheduling while atomic: qemu-system-loo/1011/0x00000002  Modules linked in: amdgpu rfkill nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat ns  CPU: 1 UID: 0 PID: 1011 Comm: qemu-system-loo Tainted: G        W          6.12.0-rc2+ #1774  Tainted: [W]=WARN  Hardware name: Loongson Loongson-3A5000-7A1000-1w-CRB/Loongson-LS3A5000-7A1000-1w-CRB, BIOS vUDK2018-LoongArch-V2.0.0-prebeta9 10/21/2022  Stack : ffffffffffffffff 0000000000000000 9000000004e3ea38 9000000116744000          90000001167475a0 0000000000000000 90000001167475a8 9000000005644830          90000000058dc000 90000000058dbff8 9000000116747420 0000000000000001          0000000000000001 6a613fc938313980 000000000790c000 90000001001c1140          00000000000003fe 0000000000000001 000000000000000d 0000000000000003          0000000000000030 00000000000003f3 000000000790c000 9000000116747830          90000000057ef000 0000000000000000 9000000005644830 0000000000000004          0000000000000000 90000000057f4b58 0000000000000001 9000000116747868          900000000451b600 9000000005644830 9000000003a13998 0000000010000020          00000000000000b0 0000000000000004 0000000000000000 0000000000071c1d          ...  Call Trace:  [\u0026lt;9000000003a13998\u0026gt;] show_stack+0x38/0x180  [\u0026lt;9000000004e3ea34\u0026gt;] dump_stack_lvl+0x84/0xc0  [\u0026lt;9000000003a71708\u0026gt;] __schedule_bug+0x48/0x60  [\u0026lt;9000000004e45734\u0026gt;] __schedule+0x1114/0x1660  [\u0026lt;9000000004e46040\u0026gt;] schedule_rtlock+0x20/0x60  [\u0026lt;9000000004e4e330\u0026gt;] rtlock_slowlock_locked+0x3f0/0x10a0  [\u0026lt;9000000004e4f038\u0026gt;] rt_spin_lock+0x58/0x80  [\u0026lt;9000000003b02d68\u0026gt;] hrtimer_cancel_wait_running+0x68/0xc0  [\u0026lt;9000000003b02e30\u0026gt;] hrtimer_cancel+0x70/0x80  [\u0026lt;ffff80000235eb70\u0026gt;] kvm_restore_timer+0x50/0x1a0 [kvm]  [\u0026lt;ffff8000023616c8\u0026gt;] kvm_arch_vcpu_load+0x68/0x2a0 [kvm]  [\u0026lt;ffff80000234c2d4\u0026gt;] kvm_sched_in+0x34/0x60 [kvm]  [\u0026lt;9000000003a749a0\u0026gt;] finish_task_switch.isra.0+0x140/0x2e0  [\u0026lt;9000000004e44a70\u0026gt;] __schedule+0x450/0x1660  [\u0026lt;9000000004e45cb0\u0026gt;] schedule+0x30/0x180  [\u0026lt;ffff800002354c70\u0026gt;] kvm_vcpu_block+0x70/0x120 [kvm]  [\u0026lt;ffff800002354d80\u0026gt;] kvm_vcpu_halt+0x60/0x3e0 [kvm]  [\u0026lt;ffff80000235b194\u0026gt;] kvm_handle_gspr+0x3f4/0x4e0 [kvm]  [\u0026lt;ffff80000235f548\u0026gt;] kvm_handle_exit+0x1c8/0x260 [kvm](CVE-2024-53089)",
  "id": "OESA-2024-2492",
  "modified": "2026-08-06T11:07:58Z",
  "published": "2024-11-29T11:07:58Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2492"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52920"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-45010"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46698"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46713"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46765"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47678"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47707"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47712"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47745"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47747"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47749"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49856"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49885"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49899"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49914"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49915"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50024"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50031"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50038"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50039"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50045"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50062"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50085"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50093"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50098"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50141"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50143"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50148"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50154"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50157"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50162"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50166"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50169"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50170"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50171"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50182"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50191"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50192"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50195"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50203"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50205"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50208"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50209"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50216"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50217"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50223"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50230"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50234"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50236"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50241"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50248"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50255"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50258"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50262"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50265"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50269"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50271"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50272"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50273"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50275"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50276"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50283"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50284"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50289"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50294"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50298"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50299"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53043"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53046"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53047"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53052"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53055"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53061"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53063"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53066"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53076"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53083"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53085"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53089"
    }
  ],
  "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-2023-52920",
    "CVE-2024-45010",
    "CVE-2024-46698",
    "CVE-2024-46713",
    "CVE-2024-46765",
    "CVE-2024-47678",
    "CVE-2024-47707",
    "CVE-2024-47712",
    "CVE-2024-47745",
    "CVE-2024-47747",
    "CVE-2024-47749",
    "CVE-2024-49856",
    "CVE-2024-49885",
    "CVE-2024-49899",
    "CVE-2024-49914",
    "CVE-2024-49915",
    "CVE-2024-50024",
    "CVE-2024-50031",
    "CVE-2024-50038",
    "CVE-2024-50039",
    "CVE-2024-50045",
    "CVE-2024-50062",
    "CVE-2024-50085",
    "CVE-2024-50093",
    "CVE-2024-50098",
    "CVE-2024-50141",
    "CVE-2024-50143",
    "CVE-2024-50148",
    "CVE-2024-50154",
    "CVE-2024-50157",
    "CVE-2024-50162",
    "CVE-2024-50166",
    "CVE-2024-50169",
    "CVE-2024-50170",
    "CVE-2024-50171",
    "CVE-2024-50182",
    "CVE-2024-50191",
    "CVE-2024-50192",
    "CVE-2024-50195",
    "CVE-2024-50203",
    "CVE-2024-50205",
    "CVE-2024-50208",
    "CVE-2024-50209",
    "CVE-2024-50216",
    "CVE-2024-50217",
    "CVE-2024-50223",
    "CVE-2024-50230",
    "CVE-2024-50234",
    "CVE-2024-50236",
    "CVE-2024-50241",
    "CVE-2024-50248",
    "CVE-2024-50255",
    "CVE-2024-50258",
    "CVE-2024-50262",
    "CVE-2024-50265",
    "CVE-2024-50269",
    "CVE-2024-50271",
    "CVE-2024-50272",
    "CVE-2024-50273",
    "CVE-2024-50275",
    "CVE-2024-50276",
    "CVE-2024-50283",
    "CVE-2024-50284",
    "CVE-2024-50289",
    "CVE-2024-50294",
    "CVE-2024-50298",
    "CVE-2024-50299",
    "CVE-2024-53043",
    "CVE-2024-53046",
    "CVE-2024-53047",
    "CVE-2024-53052",
    "CVE-2024-53055",
    "CVE-2024-53061",
    "CVE-2024-53063",
    "CVE-2024-53066",
    "CVE-2024-53076",
    "CVE-2024-53083",
    "CVE-2024-53085",
    "CVE-2024-53089"
  ]
}

OESA-2025-1079 (CVE-2024-50191)

Vulnerability from osv_openeuler – Published: 2025-01-24 11:08 – Updated: 2026-08-06 11:08 – Source website

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:

ext4: don't set SB_RDONLY after filesystem errors

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

drm/i915/hdcp: Add encoder check in hdcp2_get_capability

Add encoder check in intel_hdcp2_get_capability to avoid null pointer error.(CVE-2024-53050)

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

sched/task_stack: fix object_is_on_stack() for KASAN tagged pointers

When CONFIG_KASAN_SW_TAGS and CONFIG_KASAN_STACK are enabled, the object_is_on_stack() function may produce incorrect results due to the presence of tags in the obj pointer, while the stack pointer does not have tags. This discrepancy can lead to incorrect stack object detection and subsequently trigger warnings if CONFIG_DEBUG_OBJECTS is also enabled.

Example of the warning:

ODEBUG: object 3eff800082ea7bb0 is NOT on stack ffff800082ea0000, but annotated. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 1 at lib/debugobjects.c:557 __debug_object_init+0x330/0x364 Modules linked in: CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.0-rc5 #4 Hardware name: linux,dummy-virt (DT) pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __debug_object_init+0x330/0x364 lr : __debug_object_init+0x330/0x364 sp : ffff800082ea7b40 x29: ffff800082ea7b40 x28: 98ff0000c0164518 x27: 98ff0000c0164534 x26: ffff800082d93ec8 x25: 0000000000000001 x24: 1cff0000c00172a0 x23: 0000000000000000 x22: ffff800082d93ed0 x21: ffff800081a24418 x20: 3eff800082ea7bb0 x19: efff800000000000 x18: 0000000000000000 x17: 00000000000000ff x16: 0000000000000047 x15: 206b63617473206e x14: 0000000000000018 x13: ffff800082ea7780 x12: 0ffff800082ea78e x11: 0ffff800082ea790 x10: 0ffff800082ea79d x9 : 34d77febe173e800 x8 : 34d77febe173e800 x7 : 0000000000000001 x6 : 0000000000000001 x5 : feff800082ea74b8 x4 : ffff800082870a90 x3 : ffff80008018d3c4 x2 : 0000000000000001 x1 : ffff800082858810 x0 : 0000000000000050 Call trace: __debug_object_init+0x330/0x364 debug_object_init_on_stack+0x30/0x3c schedule_hrtimeout_range_clock+0xac/0x26c schedule_hrtimeout+0x1c/0x30 wait_task_inactive+0x1d4/0x25c kthread_bind_mask+0x28/0x98 init_rescuer+0x1e8/0x280 workqueue_init+0x1a0/0x3cc kernel_init_freeable+0x118/0x200 kernel_init+0x28/0x1f0 ret_from_fork+0x10/0x20 ---[ end trace 0000000000000000 ]--- ODEBUG: object 3eff800082ea7bb0 is NOT on stack ffff800082ea0000, but annotated. ------------[ cut here ]------------(CVE-2024-53128)

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

ALSA: usb-audio: Fix out of bounds reads when finding clock sources

The current USB-audio driver code doesn't check bLength of each descriptor at traversing for clock descriptors. That is, when a device provides a bogus descriptor with a shorter bLength, the driver might hit out-of-bounds reads.

For addressing it, this patch adds sanity checks to the validator functions for the clock descriptor traversal. When the descriptor length is shorter than expected, it's skipped in the loop.

For the clock source and clock multiplier descriptors, we can just check bLength against the sizeof() of each descriptor type. OTOH, the clock selector descriptor of UAC2 and UAC3 has an array of bNrInPins elements and two more fields at its tail, hence those have to be checked in addition to the sizeof() check.(CVE-2024-53150)

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

ocfs2: fix uninitialized value in ocfs2_file_read_iter()

Syzbot has reported the following KMSAN splat:

BUG: KMSAN: uninit-value in ocfs2_file_read_iter+0x9a4/0xf80 ocfs2_file_read_iter+0x9a4/0xf80 __io_read+0x8d4/0x20f0 io_read+0x3e/0xf0 io_issue_sqe+0x42b/0x22c0 io_wq_submit_work+0xaf9/0xdc0 io_worker_handle_work+0xd13/0x2110 io_wq_worker+0x447/0x1410 ret_from_fork+0x6f/0x90 ret_from_fork_asm+0x1a/0x30

Uninit was created at: __alloc_pages_noprof+0x9a7/0xe00 alloc_pages_mpol_noprof+0x299/0x990 alloc_pages_noprof+0x1bf/0x1e0 allocate_slab+0x33a/0x1250 slaballoc+0x12ef/0x35e0 kmem_cache_alloc_bulk_noprof+0x486/0x1330 io_alloc_req_refill+0x84/0x560 io_submit_sqes+0x172f/0x2f30 __se_sys_io_uring_enter+0x406/0x41c0 __x64_sys_io_uring_enter+0x11f/0x1a0 x64_sys_call+0x2b54/0x3ba0 do_syscall_64+0xcd/0x1e0 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Since an instance of 'struct kiocb' may be passed from the block layer with 'private' field uninitialized, introduce 'ocfs2_iocb_init_rw_locked()' and use it from where 'ocfs2_dio_end_io()' might take care, i.e. in 'ocfs2_file_read_iter()' and 'ocfs2_file_write_iter()'.(CVE-2024-53155)

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

firmware: arm_scpi: Check the DVFS OPP count returned by the firmware

Fix a kernel crash with the below call trace when the SCPI firmware returns OPP count of zero.

dvfs_info.opp_count may be zero on some platforms during the reboot test, and the kernel will crash after dereferencing the pointer to kcalloc(info->count, sizeof(*opp), GFP_KERNEL).

| Unable to handle kernel NULL pointer dereference at virtual address 0000000000000028 | Mem abort info: | ESR = 0x96000004 | Exception class = DABT (current EL), IL = 32 bits | SET = 0, FnV = 0 | EA = 0, S1PTW = 0 | Data abort info: | ISV = 0, ISS = 0x00000004 | CM = 0, WnR = 0 | user pgtable: 4k pages, 48-bit VAs, pgdp = 00000000faefa08c | [0000000000000028] pgd=0000000000000000 | Internal error: Oops: 96000004 [#1] SMP | scpi-hwmon: probe of PHYT000D:00 failed with error -110 | Process systemd-udevd (pid: 1701, stack limit = 0x00000000aaede86c) | CPU: 2 PID: 1701 Comm: systemd-udevd Not tainted 4.19.90+ #1 | Hardware name: PHYTIUM LTD Phytium FT2000/4/Phytium FT2000/4, BIOS | pstate: 60000005 (nZCv daif -PAN -UAO) | pc : scpi_dvfs_recalc_rate+0x40/0x58 [clk_scpi] | lr : clk_register+0x438/0x720 | Call trace: | scpi_dvfs_recalc_rate+0x40/0x58 [clk_scpi] | devm_clk_hw_register+0x50/0xa0 | scpi_clk_ops_init.isra.2+0xa0/0x138 [clk_scpi] | scpi_clocks_probe+0x528/0x70c [clk_scpi] | platform_drv_probe+0x58/0xa8 | really_probe+0x260/0x3d0 | driver_probe_device+0x12c/0x148 | device_driver_attach+0x74/0x98 | __driver_attach+0xb4/0xe8 | bus_for_each_dev+0x88/0xe0 | driver_attach+0x30/0x40 | bus_add_driver+0x178/0x2b0 | driver_register+0x64/0x118 | __platform_driver_register+0x54/0x60 | scpi_clocks_driver_init+0x24/0x1000 [clk_scpi] | do_one_initcall+0x54/0x220 | do_init_module+0x54/0x1c8 | load_module+0x14a4/0x1668 | __se_sys_finit_module+0xf8/0x110 | __arm64_sys_finit_module+0x24/0x30 | el0_svc_common+0x78/0x170 | el0_svc_handler+0x38/0x78 | el0_svc+0x8/0x340 | Code: 937d7c00 a94153f3 a8c27bfd f9400421 (b8606820) | ---[ end trace 06feb22469d89fa8 ]--- | Kernel panic - not syncing: Fatal exception | SMP: stopping secondary CPUs | Kernel Offset: disabled | CPU features: 0x10,a0002008 | Memory Limit: none(CVE-2024-53157)

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

soc: qcom: geni-se: fix array underflow in geni_se_clk_tbl_get()

This loop is supposed to break if the frequency returned from clk_round_rate() is the same as on the previous iteration. However, that check doesn't make sense on the first iteration through the loop. It leads to reading before the start of these->clk_perf_tbl[] array.(CVE-2024-53158)

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2024-53159)

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

rcu/kvfree: Fix data-race in __mod_timer / kvfree_call_rcu

KCSAN reports a data race when access the krcp->monitor_work.timer.expires variable in the schedule_delayed_monitor_work() function:

<snip> BUG: KCSAN: data-race in __mod_timer / kvfree_call_rcu

read to 0xffff888237d1cce8 of 8 bytes by task 10149 on cpu 1: schedule_delayed_monitor_work kernel/rcu/tree.c:3520 [inline] kvfree_call_rcu+0x3b8/0x510 kernel/rcu/tree.c:3839 trie_update_elem+0x47c/0x620 kernel/bpf/lpm_trie.c:441 bpf_map_update_value+0x324/0x350 kernel/bpf/syscall.c:203 generic_map_update_batch+0x401/0x520 kernel/bpf/syscall.c:1849 bpf_map_do_batch+0x28c/0x3f0 kernel/bpf/syscall.c:5143 __sys_bpf+0x2e5/0x7a0 __do_sys_bpf kernel/bpf/syscall.c:5741 [inline] __se_sys_bpf kernel/bpf/syscall.c:5739 [inline] __x64_sys_bpf+0x43/0x50 kernel/bpf/syscall.c:5739 x64_sys_call+0x2625/0x2d60 arch/x86/include/generated/asm/syscalls_64.h:322 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f

write to 0xffff888237d1cce8 of 8 bytes by task 56 on cpu 0: __mod_timer+0x578/0x7f0 kernel/time/timer.c:1173 add_timer_global+0x51/0x70 kernel/time/timer.c:1330 __queue_delayed_work+0x127/0x1a0 kernel/workqueue.c:2523 queue_delayed_work_on+0xdf/0x190 kernel/workqueue.c:2552 queue_delayed_work include/linux/workqueue.h:677 [inline] schedule_delayed_monitor_work kernel/rcu/tree.c:3525 [inline] kfree_rcu_monitor+0x5e8/0x660 kernel/rcu/tree.c:3643 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0x483/0x9a0 kernel/workqueue.c:3310 worker_thread+0x51d/0x6f0 kernel/workqueue.c:3391 kthread+0x1d1/0x210 kernel/kthread.c:389 ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

Reported by Kernel Concurrency Sanitizer on: CPU: 0 UID: 0 PID: 56 Comm: kworker/u8:4 Not tainted 6.12.0-rc2-syzkaller-00050-g5b7c893ed5ed #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: events_unbound kfree_rcu_monitor <snip>

kfree_rcu_monitor() rearms the work if a "krcp" has to be still offloaded and this is done without holding krcp->lock, whereas the kvfree_call_rcu() holds it.

Fix it by acquiring the "krcp->lock" for kfree_rcu_monitor() so both functions do not race anymore.(CVE-2024-53160)

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

ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit

After an insertion in TNC, the tree might split and cause a node to change its znode->parent. A further deletion of other nodes in the tree (which also could free the nodes), the aforementioned node's znode->cparent could still point to a freed node. This znode->cparent may not be updated when getting nodes to commit in ubifs_tnc_start_commit(). This could then trigger a use-after-free when accessing the znode->cparent in write_index() in ubifs_tnc_end_commit().

This can be triggered by running

rm -f /etc/test-file.bin dd if=/dev/urandom of=/etc/test-file.bin bs=1M count=60 conv=fsync

in a loop, and with CONFIG_UBIFS_FS_AUTHENTICATION. KASAN then reports:

BUG: KASAN: use-after-free in ubifs_tnc_end_commit+0xa5c/0x1950 Write of size 32 at addr ffffff800a3af86c by task ubifs_bgt0_20/153

Call trace: dump_backtrace+0x0/0x340 show_stack+0x18/0x24 dump_stack_lvl+0x9c/0xbc print_address_description.constprop.0+0x74/0x2b0 kasan_report+0x1d8/0x1f0 kasan_check_range+0xf8/0x1a0 memcpy+0x84/0xf4 ubifs_tnc_end_commit+0xa5c/0x1950 do_commit+0x4e0/0x1340 ubifs_bg_thread+0x234/0x2e0 kthread+0x36c/0x410 ret_from_fork+0x10/0x20

Allocated by task 401: kasan_save_stack+0x38/0x70 __kasan_kmalloc+0x8c/0xd0 __kmalloc+0x34c/0x5bc tnc_insert+0x140/0x16a4 ubifs_tnc_add+0x370/0x52c ubifs_jnl_write_data+0x5d8/0x870 do_writepage+0x36c/0x510 ubifs_writepage+0x190/0x4dc __writepage+0x58/0x154 write_cache_pages+0x394/0x830 do_writepages+0x1f0/0x5b0 filemap_fdatawrite_wbc+0x170/0x25c file_write_and_wait_range+0x140/0x190 ubifs_fsync+0xe8/0x290 vfs_fsync_range+0xc0/0x1e4 do_fsync+0x40/0x90 __arm64_sys_fsync+0x34/0x50 invoke_syscall.constprop.0+0xa8/0x260 do_el0_svc+0xc8/0x1f0 el0_svc+0x34/0x70 el0t_64_sync_handler+0x108/0x114 el0t_64_sync+0x1a4/0x1a8

Freed by task 403: kasan_save_stack+0x38/0x70 kasan_set_track+0x28/0x40 kasan_set_free_info+0x28/0x4c __kasan_slab_free+0xd4/0x13c kfree+0xc4/0x3a0 tnc_delete+0x3f4/0xe40 ubifs_tnc_remove_range+0x368/0x73c ubifs_tnc_remove_ino+0x29c/0x2e0 ubifs_jnl_delete_inode+0x150/0x260 ubifs_evict_inode+0x1d4/0x2e4 evict+0x1c8/0x450 iput+0x2a0/0x3c4 do_unlinkat+0x2cc/0x490 __arm64_sys_unlinkat+0x90/0x100 invoke_syscall.constprop.0+0xa8/0x260 do_el0_svc+0xc8/0x1f0 el0_svc+0x34/0x70 el0t_64_sync_handler+0x108/0x114 el0t_64_sync+0x1a4/0x1a8

The offending memcpy() in ubifs_copy_hash() has a use-after-free when a node becomes root in TNC but still has a cparent to an already freed node. More specifically, consider the following TNC:

     zroot
     /
    /
  zp1
  /
 /
zn

Inserting a new node zn_new with a key smaller then zn will trigger a split in tnc_insert() if zp1 is full:

     zroot
     /   \
    /     \
  zp1     zp2
  /         \
 /           \

zn_new zn

zn->parent has now been moved to zp2, but zn->cparent still points to zp1.

Now, consider a removal of all the nodes except zn. Just when tnc_delete() is about to delete zroot and zp2:

zroot and zp2 get freed and the tree collapses:

zn

zn now becomes the new zroot.

get_znodes_to_commit() will now only find zn, the new zroot, and write_index() will check its znode->cparent that wrongly points to the already freed zp1. ubifs_copy_hash() thus gets wrongly called with znode->cparent->zbranch[znode->iip].hash that triggers the use-after-free!

Fix this by explicitly setting znode->cparent to NULL in get_znodes_to_commit() for the root node. The search for the dirty nodes ---truncated---(CVE-2024-53171)

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

ALSA: pcm: Add sanity NULL check for the default mmap fault handler

A driver might allow the mmap access before initializing its runtime->dma_area properly. Add a proper NULL check before passing to virt_to_page() for avoiding a panic.(CVE-2024-53180)

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

io_uring: check for overflows in io_pin_pages

WARNING: CPU: 0 PID: 5834 at io_uring/memmap.c:144 io_pin_pages+0x149/0x180 io_uring/memmap.c:144 CPU: 0 UID: 0 PID: 5834 Comm: syz-executor825 Not tainted 6.12.0-next-20241118-syzkaller #0 Call Trace: <TASK> __io_uaddr_map+0xfb/0x2d0 io_uring/memmap.c:183 io_rings_map io_uring/io_uring.c:2611 [inline] io_allocate_scq_urings+0x1c0/0x650 io_uring/io_uring.c:3470 io_uring_create+0x5b5/0xc00 io_uring/io_uring.c:3692 io_uring_setup io_uring/io_uring.c:3781 [inline] ... </TASK>

io_pin_pages()'s uaddr parameter came directly from the user and can be garbage. Don't just add size to it as it can overflow.(CVE-2024-53187)

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

wifi: rtlwifi: Drastically reduce the attempts to read efuse in case of failures

Syzkaller reported a hung task with uevent_show() on stack trace. That specific issue was addressed by another commit [0], but even with that fix applied (for example, running v6.12-rc5) we face another type of hung task that comes from the same reproducer [1]. By investigating that, we could narrow it to the following path:

(a) Syzkaller emulates a Realtek USB WiFi adapter using raw-gadget and dummy_hcd infrastructure.

(b) During the probe of rtl8192cu, the driver ends-up performing an efuse read procedure (which is related to EEPROM load IIUC), and here lies the issue: the function read_efuse() calls read_efuse_byte() many times, as loop iterations depending on the efuse size (in our example, 512 in total).

This procedure for reading efuse bytes relies in a loop that performs an I/O read up to 10k times in case of failures. We measured the time of the loop inside read_efuse_byte() alone, and in this reproducer (which involves the dummy_hcd emulation layer), it takes 15 seconds each. As a consequence, we have the driver stuck in its probe routine for big time, exposing a stack trace like below if we attempt to reboot the system, for example:

task:kworker/0:3 state:D stack:0 pid:662 tgid:662 ppid:2 flags:0x00004000 Workqueue: usb_hub_wq hub_event Call Trace: __schedule+0xe22/0xeb6 schedule_timeout+0xe7/0x132 __wait_for_common+0xb5/0x12e usb_start_wait_urb+0xc5/0x1ef ? usb_alloc_urb+0x95/0xa4 usb_control_msg+0xff/0x184 _usbctrl_vendorreq_sync+0xa0/0x161 _usb_read_sync+0xb3/0xc5 read_efuse_byte+0x13c/0x146 read_efuse+0x351/0x5f0 efuse_read_all_map+0x42/0x52 rtl_efuse_shadow_map_update+0x60/0xef rtl_get_hwinfo+0x5d/0x1c2 rtl92cu_read_eeprom_info+0x10a/0x8d5 ? rtl92c_read_chip_version+0x14f/0x17e rtl_usb_probe+0x323/0x851 usb_probe_interface+0x278/0x34b really_probe+0x202/0x4a4 __driver_probe_device+0x166/0x1b2 driver_probe_device+0x2f/0xd8 [...]

We propose hereby to drastically reduce the attempts of doing the I/O reads in case of failures, restricted to USB devices (given that they're inherently slower than PCIe ones). By retrying up to 10 times (instead of 10000), we got reponsiveness in the reproducer, while seems reasonable to believe that there's no sane USB device implementation in the field requiring this amount of retries at every I/O read in order to properly work. Based on that assumption, it'd be good to have it backported to stable but maybe not since driver implementation (the 10k number comes from day 0), perhaps up to 6.x series makes sense.

[0] Commit 15fffc6a5624 ("driver core: Fix uevent_show() vs driver detach race")

[1] A note about that: this syzkaller report presents multiple reproducers that differs by the type of emulated USB device. For this specific case, check the entry from 2024/08/08 06:23 in the list of crashes; the C repro is available at https://syzkaller.appspot.com/text?tag=ReproC&x=1521fc83980000.(CVE-2024-53190)

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

wifi: ath12k: fix warning when unbinding

If there is an error during some initialization related to firmware, the buffers dp->tx_ring[i].tx_status are released. However this is released again when the device is unbinded (ath12k_pci), and we get: WARNING: CPU: 0 PID: 2098 at mm/slub.c:4689 free_large_kmalloc+0x4d/0x80 Call Trace: free_large_kmalloc ath12k_dp_free ath12k_core_deinit ath12k_pci_remove ...

The issue is always reproducible from a VM because the MSI addressing initialization is failing.

In order to fix the issue, just set the buffers to NULL after releasing in order to avoid the double free.(CVE-2024-53191)

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

PCI: Fix use-after-free of slot->bus on hot remove

Dennis reports a boot crash on recent Lenovo laptops with a USB4 dock.

Since commit 0fc70886569c ("thunderbolt: Reset USB4 v2 host router") and commit 59a54c5f3dbd ("thunderbolt: Reset topology created by the boot firmware"), USB4 v2 and v1 Host Routers are reset on probe of the thunderbolt driver.

The reset clears the Presence Detect State and Data Link Layer Link Active bits at the USB4 Host Router's Root Port and thus causes hot removal of the dock.

The crash occurs when pciehp is unbound from one of the dock's Downstream Ports: pciehp creates a pci_slot on bind and destroys it on unbind. The pci_slot contains a pointer to the pci_bus below the Downstream Port, but a reference on that pci_bus is never acquired. The pci_bus is destroyed before the pci_slot, so a use-after-free ensues when pci_slot_release() accesses slot->bus.

In principle this should not happen because pci_stop_bus_device() unbinds pciehp (and therefore destroys the pci_slot) before the pci_bus is destroyed by pci_remove_bus_device().

However the stacktrace provided by Dennis shows that pciehp is unbound from pci_remove_bus_device() instead of pci_stop_bus_device(). To understand the significance of this, one needs to know that the PCI core uses a two step process to remove a portion of the hierarchy: It first unbinds all drivers in the sub-hierarchy in pci_stop_bus_device() and then actually removes the devices in pci_remove_bus_device(). There is no precaution to prevent driver binding in-between pci_stop_bus_device() and pci_remove_bus_device().

In Dennis' case, it seems removal of the hierarchy by pciehp races with driver binding by pci_bus_add_devices(). pciehp is bound to the Downstream Port after pci_stop_bus_device() has run, so it is unbound by pci_remove_bus_device() instead of pci_stop_bus_device(). Because the pci_bus has already been destroyed at that point, accesses to it result in a use-after-free.

One might conclude that driver binding needs to be prevented after pci_stop_bus_device() has run. However it seems risky that pci_slot points to pci_bus without holding a reference. Solely relying on correct ordering of driver unbind versus pci_bus destruction is certainly not defensive programming.

If pci_slot has a need to access data in pci_bus, it ought to acquire a reference. Amend pci_create_slot() accordingly. Dennis reports that the crash is not reproducible with this change.

Abridged stacktrace:

pcieport 0000:00:07.0: PME: Signaling with IRQ 156 pcieport 0000:00:07.0: pciehp: Slot #12 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ IbPresDis- LLActRep+ pci_bus 0000:20: dev 00, created physical slot 12 pcieport 0000:00:07.0: pciehp: Slot(12): Card not present ... pcieport 0000:21:02.0: pciehp: pcie_disable_notification: SLOTCTRL d8 write cmd 0 Oops: general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b6b6b: 0000 [#1] PREEMPT SMP NOPTI CPU: 13 UID: 0 PID: 134 Comm: irq/156-pciehp Not tainted 6.11.0-devel+ #1 RIP: 0010:dev_driver_string+0x12/0x40 pci_destroy_slot pciehp_remove pcie_port_remove_service device_release_driver_internal bus_remove_device device_del device_unregister remove_iter device_for_each_child pcie_portdrv_remove pci_device_remove device_release_driver_internal bus_remove_device device_del pci_remove_bus_device (recursive invocation) pci_remove_bus_device pciehp_unconfigure_device pciehp_disable_slot pciehp_handle_presence_or_link_change pciehp_ist(CVE-2024-53194)

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

KVM: arm64: Don't retire aborted MMIO instruction

Returning an abort to the guest for an unsupported MMIO access is a documented feature of the KVM UAPI. Nevertheless, it's clear that this plumbing has seen limited testing, since userspace can trivially cause a WARN in the MMIO return:

WARNING: CPU: 0 PID: 30558 at arch/arm64/include/asm/kvm_emulate.h:536 kvm_handle_mmio_return+0x46c/0x5c4 arch/arm64/include/asm/kvm_emulate.h:536 Call trace: kvm_handle_mmio_return+0x46c/0x5c4 arch/arm64/include/asm/kvm_emulate.h:536 kvm_arch_vcpu_ioctl_run+0x98/0x15b4 arch/arm64/kvm/arm.c:1133 kvm_vcpu_ioctl+0x75c/0xa78 virt/kvm/kvm_main.c:4487 __do_sys_ioctl fs/ioctl.c:51 [inline] __se_sys_ioctl fs/ioctl.c:893 [inline] __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:893 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x1e0/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x38/0x68 arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x90/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598

The splat is complaining that KVM is advancing PC while an exception is pending, i.e. that KVM is retiring the MMIO instruction despite a pending synchronous external abort. Womp womp.

Fix the glaring UAPI bug by skipping over all the MMIO emulation in case there is a pending synchronous exception. Note that while userspace is capable of pending an asynchronous exception (SError, IRQ, or FIQ), it is still safe to retire the MMIO instruction in this case as (1) they are by definition asynchronous, and (2) KVM relies on hardware support for pending/delivering these exceptions instead of the software state machine for advancing PC.(CVE-2024-53196)

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

usb: typec: fix potential array underflow in ucsi_ccg_sync_control()

The "command" variable can be controlled by the user via debugfs. The worry is that if con_index is zero then "&uc->ucsi->connector[con_index - 1]" would be an array underflow.(CVE-2024-53203)

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

net: usb: lan78xx: Fix double free issue with interrupt buffer allocation

In lan78xx_probe(), the buffer buf was being freed twice: once implicitly through usb_free_urb(dev->urb_intr) with the URB_FREE_BUFFER flag and again explicitly by kfree(buf). This caused a double free issue.

To resolve this, reordered kmalloc() and usb_alloc_urb() calls to simplify the initialization sequence and removed the redundant kfree(buf). Now, buf is allocated after usb_alloc_urb(), ensuring it is correctly managed by usb_fill_int_urb() and freed by usb_free_urb() as intended.(CVE-2024-53213)

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

svcrdma: fix miss destroy percpu_counter in svc_rdma_proc_init()

There's issue as follows: RPC: Registered rdma transport module. RPC: Registered rdma backchannel transport module. RPC: Unregistered rdma transport module. RPC: Unregistered rdma backchannel transport module. BUG: unable to handle page fault for address: fffffbfff80c609a PGD 123fee067 P4D 123fee067 PUD 123fea067 PMD 10c624067 PTE 0 Oops: Oops: 0000 [#1] PREEMPT SMP KASAN NOPTI RIP: 0010:percpu_counter_destroy_many+0xf7/0x2a0 Call Trace: <TASK> __die+0x1f/0x70 page_fault_oops+0x2cd/0x860 spurious_kernel_fault+0x36/0x450 do_kern_addr_fault+0xca/0x100 exc_page_fault+0x128/0x150 asm_exc_page_fault+0x26/0x30 percpu_counter_destroy_many+0xf7/0x2a0 mmdrop+0x209/0x350 finish_task_switch.isra.0+0x481/0x840 schedule_tail+0xe/0xd0 ret_from_fork+0x23/0x80 ret_from_fork_asm+0x1a/0x30 </TASK>

If register_sysctl() return NULL, then svc_rdma_proc_cleanup() will not destroy the percpu counters which init in svc_rdma_proc_init(). If CONFIG_HOTPLUG_CPU is enabled, residual nodes may be in the 'percpu_counters' list. The above issue may occur once the module is removed. If the CONFIG_HOTPLUG_CPU configuration is not enabled, memory leakage occurs. To solve above issue just destroy all percpu counters when register_sysctl() return NULL.(CVE-2024-53215)

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

f2fs: fix race in concurrent f2fs_stop_gc_thread

In my test case, concurrent calls to f2fs shutdown report the following stack trace:

Oops: general protection fault, probably for non-canonical address 0xc6cfff63bb5513fc: 0000 [#1] PREEMPT SMP PTI CPU: 0 UID: 0 PID: 678 Comm: f2fs_rep_shutdo Not tainted 6.12.0-rc5-next-20241029-g6fb2fa9805c5-dirty #85 Call Trace: <TASK> ? show_regs+0x8b/0xa0 ? __die_body+0x26/0xa0 ? die_addr+0x54/0x90 ? exc_general_protection+0x24b/0x5c0 ? asm_exc_general_protection+0x26/0x30 ? kthread_stop+0x46/0x390 f2fs_stop_gc_thread+0x6c/0x110 f2fs_do_shutdown+0x309/0x3a0 f2fs_ioc_shutdown+0x150/0x1c0 __f2fs_ioctl+0xffd/0x2ac0 f2fs_ioctl+0x76/0xe0 vfs_ioctl+0x23/0x60 __x64_sys_ioctl+0xce/0xf0 x64_sys_call+0x2b1b/0x4540 do_syscall_64+0xa7/0x240 entry_SYSCALL_64_after_hwframe+0x76/0x7e

The root cause is a race condition in f2fs_stop_gc_thread() called from different f2fs shutdown paths:

[CPU0] [CPU1] ---------------------- ----------------------- f2fs_stop_gc_thread f2fs_stop_gc_thread gc_th = sbi->gc_thread gc_th = sbi->gc_thread kfree(gc_th) sbi->gc_thread = NULL < gc_th != NULL > kthread_stop(gc_th->f2fs_gc_task) //UAF

The commit c7f114d864ac ("f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread()") attempted to fix this issue by using a read semaphore to prevent races between shutdown and remount threads, but it fails to prevent all race conditions.

Fix it by converting to write lock of s_umount in f2fs_do_shutdown().(CVE-2024-53218)

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

virtiofs: use pages instead of pointer for kernel direct IO

When trying to insert a 10MB kernel module kept in a virtio-fs with cache disabled, the following warning was reported:

------------[ cut here ]------------ WARNING: CPU: 1 PID: 404 at mm/page_alloc.c:4551 ...... Modules linked in: CPU: 1 PID: 404 Comm: insmod Not tainted 6.9.0-rc5+ #123 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) ...... RIP: 0010:__alloc_pages+0x2bf/0x380 ...... Call Trace: <TASK> ? __warn+0x8e/0x150 ? __alloc_pages+0x2bf/0x380 __kmalloc_large_node+0x86/0x160 __kmalloc+0x33c/0x480 virtio_fs_enqueue_req+0x240/0x6d0 virtio_fs_wake_pending_and_unlock+0x7f/0x190 queue_request_and_unlock+0x55/0x60 fuse_simple_request+0x152/0x2b0 fuse_direct_io+0x5d2/0x8c0 fuse_file_read_iter+0x121/0x160 __kernel_read+0x151/0x2d0 kernel_read+0x45/0x50 kernel_read_file+0x1a9/0x2a0 init_module_from_file+0x6a/0xe0 idempotent_init_module+0x175/0x230 __x64_sys_finit_module+0x5d/0xb0 x64_sys_call+0x1c3/0x9e0 do_syscall_64+0x3d/0xc0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 ...... </TASK> ---[ end trace 0000000000000000 ]---

The warning is triggered as follows:

1) syscall finit_module() handles the module insertion and it invokes kernel_read_file() to read the content of the module first.

2) kernel_read_file() allocates a 10MB buffer by using vmalloc() and passes it to kernel_read(). kernel_read() constructs a kvec iter by using iov_iter_kvec() and passes it to fuse_file_read_iter().

3) virtio-fs disables the cache, so fuse_file_read_iter() invokes fuse_direct_io(). As for now, the maximal read size for kvec iter is only limited by fc->max_read. For virtio-fs, max_read is UINT_MAX, so fuse_direct_io() doesn't split the 10MB buffer. It saves the address and the size of the 10MB-sized buffer in out_args[0] of a fuse request and passes the fuse request to virtio_fs_wake_pending_and_unlock().

4) virtio_fs_wake_pending_and_unlock() uses virtio_fs_enqueue_req() to queue the request. Because virtiofs need DMA-able address, so virtio_fs_enqueue_req() uses kmalloc() to allocate a bounce buffer for all fuse args, copies these args into the bounce buffer and passed the physical address of the bounce buffer to virtiofsd. The total length of these fuse args for the passed fuse request is about 10MB, so copy_args_to_argbuf() invokes kmalloc() with a 10MB size parameter and it triggers the warning in __alloc_pages():

if (WARN_ON_ONCE_GFP(order &gt; MAX_PAGE_ORDER, gfp))
    return NULL;

5) virtio_fs_enqueue_req() will retry the memory allocation in a kworker, but it won't help, because kmalloc() will always return NULL due to the abnormal size and finit_module() will hang forever.

A feasible solution is to limit the value of max_read for virtio-fs, so the length passed to kmalloc() will be limited. However it will affect the maximal read size for normal read. And for virtio-fs write initiated from kernel, it has the similar problem but now there is no way to limit fc->max_write in kernel.

So instead of limiting both the values of max_read and max_write in kernel, introducing use_pages_for_kvec_io in fuse_conn and setting it as true in virtiofs. When use_pages_for_kvec_io is enabled, fuse will use pages instead of pointer to pass the KVEC_IO data.

After switching to pages for KVEC_IO data, these pages will be used for DMA through virtio-fs. If these pages are backed by vmalloc(), {flush|invalidate}_kernel_vmap_range() are necessary to flush or invalidate the cache before the DMA operation. So add two new fields in fuse_args_pages to record the base address of vmalloc area and the condition indicating whether invalidation is needed. Perform the flush in fuse_get_user_pages() for write operations and the invalidation in fuse_release_user_pages() for read operations.

It may seem necessary to introduce another fie ---truncated---(CVE-2024-53219)

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

RDMA/mlx5: Move events notifier registration to be after device registration

Move pkey change work initialization and cleanup from device resources stage to notifier stage, since this is the stage which handles this work events.

Fix a race between the device deregistration and pkey change work by moving MLX5_IB_STAGE_DEVICE_NOTIFIER to be after MLX5_IB_STAGE_IB_REG in order to ensure that the notifier is deregistered before the device during cleanup. Which ensures there are no works that are being executed after the device has already unregistered which can cause the panic below.

BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 630071 Comm: kworker/1:2 Kdump: loaded Tainted: G W OE --------- --- 5.14.0-162.6.1.el9_1.x86_64 #1 Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 02/27/2023 Workqueue: events pkey_change_handler [mlx5_ib] RIP: 0010:setup_qp+0x38/0x1f0 [mlx5_ib] Code: ee 41 54 45 31 e4 55 89 f5 53 48 89 fb 48 83 ec 20 8b 77 08 65 48 8b 04 25 28 00 00 00 48 89 44 24 18 48 8b 07 48 8d 4c 24 16 <4c> 8b 38 49 8b 87 80 0b 00 00 4c 89 ff 48 8b 80 08 05 00 00 8b 40 RSP: 0018:ffffbcc54068be20 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff954054494128 RCX: ffffbcc54068be36 RDX: ffff954004934000 RSI: 0000000000000001 RDI: ffff954054494128 RBP: 0000000000000023 R08: ffff954001be2c20 R09: 0000000000000001 R10: ffff954001be2c20 R11: ffff9540260133c0 R12: 0000000000000000 R13: 0000000000000023 R14: 0000000000000000 R15: ffff9540ffcb0905 FS: 0000000000000000(0000) GS:ffff9540ffc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 000000010625c001 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: mlx5_ib_gsi_pkey_change+0x20/0x40 [mlx5_ib] process_one_work+0x1e8/0x3c0 worker_thread+0x50/0x3b0 ? rescuer_thread+0x380/0x380 kthread+0x149/0x170 ? set_kthread_struct+0x50/0x50 ret_from_fork+0x22/0x30 Modules linked in: rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_umad(OE) mlx5_ib(OE) mlx5_fwctl(OE) fwctl(OE) ib_uverbs(OE) mlx5_core(OE) mlxdevm(OE) ib_core(OE) mlx_compat(OE) psample mlxfw(OE) tls knem(OE) netconsole nfsv3 nfs_acl nfs lockd grace fscache netfs qrtr rfkill sunrpc intel_rapl_msr intel_rapl_common rapl hv_balloon hv_utils i2c_piix4 pcspkr joydev fuse ext4 mbcache jbd2 sr_mod sd_mod cdrom t10_pi sg ata_generic pci_hyperv pci_hyperv_intf hyperv_drm drm_shmem_helper drm_kms_helper hv_storvsc syscopyarea hv_netvsc sysfillrect sysimgblt hid_hyperv fb_sys_fops scsi_transport_fc hyperv_keyboard drm ata_piix crct10dif_pclmul crc32_pclmul crc32c_intel libata ghash_clmulni_intel hv_vmbus serio_raw [last unloaded: ib_core] CR2: 0000000000000000 ---[ end trace f6f8be4eae12f7bc ]---(CVE-2024-53224)

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

RDMA/rxe: Fix the qp flush warnings in req

When the qp is in error state, the status of WQEs in the queue should be set to error. Or else the following will appear.

[ 920.617269] WARNING: CPU: 1 PID: 21 at drivers/infiniband/sw/rxe/rxe_comp.c:756 rxe_completer+0x989/0xcc0 [rdma_rxe] [ 920.617744] Modules linked in: rnbd_client(O) rtrs_client(O) rtrs_core(O) rdma_ucm rdma_cm iw_cm ib_cm crc32_generic rdma_rxe ip6_udp_tunnel udp_tunnel ib_uverbs ib_core loop brd null_blk ipv6 [ 920.618516] CPU: 1 PID: 21 Comm: ksoftirqd/1 Tainted: G O 6.1.113-storage+ #65 [ 920.618986] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 [ 920.619396] RIP: 0010:rxe_completer+0x989/0xcc0 [rdma_rxe] [ 920.619658] Code: 0f b6 84 24 3a 02 00 00 41 89 84 24 44 04 00 00 e9 2a f7 ff ff 39 ca bb 03 00 00 00 b8 0e 00 00 00 48 0f 45 d8 e9 15 f7 ff ff <0f> 0b e9 cb f8 ff ff 41 bf f5 ff ff ff e9 08 f8 ff ff 49 8d bc 24 [ 920.620482] RSP: 0018:ffff97b7c00bbc38 EFLAGS: 00010246 [ 920.620817] RAX: 0000000000000000 RBX: 000000000000000c RCX: 0000000000000008 [ 920.621183] RDX: ffff960dc396ebc0 RSI: 0000000000005400 RDI: ffff960dc4e2fbac [ 920.621548] RBP: 0000000000000000 R08: 0000000000000001 R09: ffffffffac406450 [ 920.621884] R10: ffffffffac4060c0 R11: 0000000000000001 R12: ffff960dc4e2f800 [ 920.622254] R13: ffff960dc4e2f928 R14: ffff97b7c029c580 R15: 0000000000000000 [ 920.622609] FS: 0000000000000000(0000) GS:ffff960ef7d00000(0000) knlGS:0000000000000000 [ 920.622979] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 920.623245] CR2: 00007fa056965e90 CR3: 00000001107f1000 CR4: 00000000000006e0 [ 920.623680] Call Trace: [ 920.623815] <TASK> [ 920.623933] ? __warn+0x79/0xc0 [ 920.624116] ? rxe_completer+0x989/0xcc0 [rdma_rxe] [ 920.624356] ? report_bug+0xfb/0x150 [ 920.624594] ? handle_bug+0x3c/0x60 [ 920.624796] ? exc_invalid_op+0x14/0x70 [ 920.624976] ? asm_exc_invalid_op+0x16/0x20 [ 920.625203] ? rxe_completer+0x989/0xcc0 [rdma_rxe] [ 920.625474] ? rxe_completer+0x329/0xcc0 [rdma_rxe] [ 920.625749] rxe_do_task+0x80/0x110 [rdma_rxe] [ 920.626037] rxe_requester+0x625/0xde0 [rdma_rxe] [ 920.626310] ? rxe_cq_post+0xe2/0x180 [rdma_rxe] [ 920.626583] ? do_complete+0x18d/0x220 [rdma_rxe] [ 920.626812] ? rxe_completer+0x1a3/0xcc0 [rdma_rxe] [ 920.627050] rxe_do_task+0x80/0x110 [rdma_rxe] [ 920.627285] tasklet_action_common.constprop.0+0xa4/0x120 [ 920.627522] handle_softirqs+0xc2/0x250 [ 920.627728] ? sort_range+0x20/0x20 [ 920.627942] run_ksoftirqd+0x1f/0x30 [ 920.628158] smpboot_thread_fn+0xc7/0x1b0 [ 920.628334] kthread+0xd6/0x100 [ 920.628504] ? kthread_complete_and_exit+0x20/0x20 [ 920.628709] ret_from_fork+0x1f/0x30 [ 920.628892] </TASK>(CVE-2024-53229)

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

cpufreq: CPPC: Fix possible null-ptr-deref for cpufreq_cpu_get_raw()

cpufreq_cpu_get_raw() may return NULL if the cpu is not in policy->cpus cpu mask and it will cause null pointer dereference.(CVE-2024-53231)

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

erofs: handle NONHEAD !delta[1] lclusters gracefully

syzbot reported a WARNING in iomap_iter_done: iomap_fiemap+0x73b/0x9b0 fs/iomap/fiemap.c:80 ioctl_fiemap fs/ioctl.c:220 [inline]

Generally, NONHEAD lclusters won't have delta[1]==0, except for crafted images and filesystems created by pre-1.0 mkfs versions.

Previously, it would immediately bail out if delta[1]==0, which led to inadequate decompressed lengths (thus FIEMAP is impacted). Treat it as delta[1]=1 to work around these legacy mkfs versions.

lclusterbits > 14 is illegal for compact indexes, error out too.(CVE-2024-53234)

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

ALSA: 6fire: Release resources at card release

The current 6fire code tries to release the resources right after the call of usb6fire_chip_abort(). But at this moment, the card object might be still in use (as we're calling snd_card_free_when_closed()).

For avoid potential UAFs, move the release of resources to the card's private_free instead of the manual call of usb6fire_chip_destroy() at the USB disconnect callback.(CVE-2024-53239)

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

x86/xen: don't do PV iret hypercall through hypercall page

Instead of jumping to the Xen hypercall page for doing the iret hypercall, directly code the required sequence in xen-asm.S.

This is done in preparation of no longer using hypercall page at all, as it has shown to cause problems with speculation mitigations.

This is part of XSA-466 / CVE-2024-53241.(CVE-2024-53241)

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

net: renesas: rswitch: avoid use-after-put for a device tree node

The device tree node saved in the rswitch_device structure is used at several driver locations. So passing this node to of_node_put() after the first use is wrong.

Move of_node_put() for this node to exit paths.(CVE-2024-55639)

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

wifi: ath12k: Skip Rx TID cleanup for self peer

During peer create, dp setup for the peer is done where Rx TID is updated for all the TIDs. Peer object for self peer will not go through dp setup.

When core halts, dp cleanup is done for all the peers. While cleanup, rx_tid::ab is accessed which causes below stack trace for self peer.

WARNING: CPU: 6 PID: 12297 at drivers/net/wireless/ath/ath12k/dp_rx.c:851 Call Trace: __warn+0x7b/0x1a0 ath12k_dp_rx_frags_cleanup+0xd2/0xe0 [ath12k] report_bug+0x10b/0x200 handle_bug+0x3f/0x70 exc_invalid_op+0x13/0x60 asm_exc_invalid_op+0x16/0x20 ath12k_dp_rx_frags_cleanup+0xd2/0xe0 [ath12k] ath12k_dp_rx_frags_cleanup+0xca/0xe0 [ath12k] ath12k_dp_rx_peer_tid_cleanup+0x39/0xa0 [ath12k] ath12k_mac_peer_cleanup_all+0x61/0x100 [ath12k] ath12k_core_halt+0x3b/0x100 [ath12k] ath12k_core_reset+0x494/0x4c0 [ath12k]

sta object in peer will be updated when remote peer is created. Hence use peer::sta to detect the self peer and skip the cleanup.

Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1 Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3(CVE-2024-56543)

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

drivers: soc: xilinx: add the missing kfree in xlnx_add_cb_for_suspend()

If we fail to allocate memory for cb_data by kmalloc, the memory allocation for eve_data is never freed, add the missing kfree() in the error handling path.(CVE-2024-56546)

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

cachefiles: Fix NULL pointer dereference in object->file

At present, the object->file has the NULL pointer dereference problem in ondemand-mode. The root cause is that the allocated fd and object->file lifetime are inconsistent, and the user-space invocation to anon_fd uses object->file. Following is the process that triggers the issue:

  [write fd]                [umount]

cachefiles_ondemand_fd_write_iter fscache_cookie_state_machine cachefiles_withdraw_cookie if (!file) return -ENOBUFS cachefiles_clean_up_object cachefiles_unmark_inode_in_use fput(object->file) object->file = NULL // file NULL pointer dereference! __cachefiles_write(..., file, ...)

Fix this issue by add an additional reference count to the object->file before write/llseek, and decrement after it finished.(CVE-2024-56549)

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

i3c: master: Fix miss free init_dyn_addr at i3c_master_put_i3c_addrs()

if (dev->boardinfo && dev->boardinfo->init_dyn_addr) ^^^ here check "init_dyn_addr" i3c_bus_set_addr_slot_status(&master->bus, dev->info.dyn_addr, ...) ^^^^ free "dyn_addr" Fix copy/paste error "dyn_addr" by replacing it with "init_dyn_addr".(CVE-2024-56562)

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

ovl: Filter invalid inodes with missing lookup function

Add a check to the ovl_dentry_weird() function to prevent the processing of directory inodes that lack the lookup function. This is important because such inodes can cause errors in overlayfs when passed to the lowerstack.(CVE-2024-56570)

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

media: platform: allegro-dvt: Fix possible memory leak in allocate_buffers_internal()

The buffer in the loop should be released under the exception path, otherwise there may be a memory leak here.

To mitigate this, free the buffer when allegro_alloc_buffer fails.(CVE-2024-56572)

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

btrfs: fix use-after-free in btrfs_encoded_read_endio()

Shinichiro reported the following use-after free that sometimes is happening in our CI system when running fstests' btrfs/284 on a TCMU runner device:

BUG: KASAN: slab-use-after-free in lock_release+0x708/0x780 Read of size 8 at addr ffff888106a83f18 by task kworker/u80:6/219

CPU: 8 UID: 0 PID: 219 Comm: kworker/u80:6 Not tainted 6.12.0-rc6-kts+ #15 Hardware name: Supermicro Super Server/X11SPi-TF, BIOS 3.3 02/21/2020 Workqueue: btrfs-endio btrfs_end_bio_work [btrfs] Call Trace: <TASK> dump_stack_lvl+0x6e/0xa0 ? lock_release+0x708/0x780 print_report+0x174/0x505 ? lock_release+0x708/0x780 ? __virt_addr_valid+0x224/0x410 ? lock_release+0x708/0x780 kasan_report+0xda/0x1b0 ? lock_release+0x708/0x780 ? __wake_up+0x44/0x60 lock_release+0x708/0x780 ? __pfx_lock_release+0x10/0x10 ? __pfx_do_raw_spin_lock+0x10/0x10 ? lock_is_held_type+0x9a/0x110 _raw_spin_unlock_irqrestore+0x1f/0x60 __wake_up+0x44/0x60 btrfs_encoded_read_endio+0x14b/0x190 [btrfs] btrfs_check_read_bio+0x8d9/0x1360 [btrfs] ? lock_release+0x1b0/0x780 ? trace_lock_acquire+0x12f/0x1a0 ? __pfx_btrfs_check_read_bio+0x10/0x10 [btrfs] ? process_one_work+0x7e3/0x1460 ? lock_acquire+0x31/0xc0 ? process_one_work+0x7e3/0x1460 process_one_work+0x85c/0x1460 ? __pfx_process_one_work+0x10/0x10 ? assign_work+0x16c/0x240 worker_thread+0x5e6/0xfc0 ? __pfx_worker_thread+0x10/0x10 kthread+0x2c3/0x3a0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x31/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK>

Allocated by task 3661: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0xaa/0xb0 btrfs_encoded_read_regular_fill_pages+0x16c/0x6d0 [btrfs] send_extent_data+0xf0f/0x24a0 [btrfs] process_extent+0x48a/0x1830 [btrfs] changed_cb+0x178b/0x2ea0 [btrfs] btrfs_ioctl_send+0x3bf9/0x5c20 [btrfs] _btrfs_ioctl_send+0x117/0x330 [btrfs] btrfs_ioctl+0x184a/0x60a0 [btrfs] __x64_sys_ioctl+0x12e/0x1a0 do_syscall_64+0x95/0x180 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Freed by task 3661: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x70 __kasan_slab_free+0x4f/0x70 kfree+0x143/0x490 btrfs_encoded_read_regular_fill_pages+0x531/0x6d0 [btrfs] send_extent_data+0xf0f/0x24a0 [btrfs] process_extent+0x48a/0x1830 [btrfs] changed_cb+0x178b/0x2ea0 [btrfs] btrfs_ioctl_send+0x3bf9/0x5c20 [btrfs] _btrfs_ioctl_send+0x117/0x330 [btrfs] btrfs_ioctl+0x184a/0x60a0 [btrfs] __x64_sys_ioctl+0x12e/0x1a0 do_syscall_64+0x95/0x180 entry_SYSCALL_64_after_hwframe+0x76/0x7e

The buggy address belongs to the object at ffff888106a83f00 which belongs to the cache kmalloc-rnd-07-96 of size 96 The buggy address is located 24 bytes inside of freed 96-byte region [ffff888106a83f00, ffff888106a83f60)

The buggy address belongs to the physical page: page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888106a83800 pfn:0x106a83 flags: 0x17ffffc0000000(node=0|zone=2|lastcpupid=0x1fffff) page_type: f5(slab) raw: 0017ffffc0000000 ffff888100053680 ffffea0004917200 0000000000000004 raw: ffff888106a83800 0000000080200019 00000001f5000000 0000000000000000 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffff888106a83e00: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc ffff888106a83e80: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc >ffff888106a83f00: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc ^ ffff888106a83f80: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc ffff888106a84000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================

Further analyzing the trace and ---truncated---(CVE-2024-56582)

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

sched/deadline: Fix warning in migrate_enable for boosted tasks

When running the following command:

while true; do stress-ng --cyclic 30 --timeout 30s --minimize --quiet done

a warning is eventually triggered:

WARNING: CPU: 43 PID: 2848 at kernel/sched/deadline.c:794 setup_new_dl_entity+0x13e/0x180 ... Call Trace: <TASK> ? show_trace_log_lvl+0x1c4/0x2df ? enqueue_dl_entity+0x631/0x6e0 ? setup_new_dl_entity+0x13e/0x180 ? __warn+0x7e/0xd0 ? report_bug+0x11a/0x1a0 ? handle_bug+0x3c/0x70 ? exc_invalid_op+0x14/0x70 ? asm_exc_invalid_op+0x16/0x20 enqueue_dl_entity+0x631/0x6e0 enqueue_task_dl+0x7d/0x120 __do_set_cpus_allowed+0xe3/0x280 __set_cpus_allowed_ptr_locked+0x140/0x1d0 __set_cpus_allowed_ptr+0x54/0xa0 migrate_enable+0x7e/0x150 rt_spin_unlock+0x1c/0x90 group_send_sig_info+0xf7/0x1a0 ? kill_pid_info+0x1f/0x1d0 kill_pid_info+0x78/0x1d0 kill_proc_info+0x5b/0x110 __x64_sys_kill+0x93/0xc0 do_syscall_64+0x5c/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 RIP: 0033:0x7f0dab31f92b

This warning occurs because set_cpus_allowed dequeues and enqueues tasks with the ENQUEUE_RESTORE flag set. If the task is boosted, the warning is triggered. A boosted task already had its parameters set by rt_mutex_setprio, and a new call to setup_new_dl_entity is unnecessary, hence the WARN_ON call.

Check if we are requeueing a boosted task and avoid calling setup_new_dl_entity if that's the case.(CVE-2024-56583)

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

LoongArch: Fix sleeping in atomic context for PREEMPT_RT

Commit bab1c299f3945ffe79 ("LoongArch: Fix sleeping in atomic context in setup_tlb_handler()") changes the gfp flag from GFP_KERNEL to GFP_ATOMIC for alloc_pages_node(). However, for PREEMPT_RT kernels we can still get a "sleeping in atomic context" error:

[ 0.372259] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48 [ 0.372266] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1 [ 0.372268] preempt_count: 1, expected: 0 [ 0.372270] RCU nest depth: 1, expected: 1 [ 0.372272] 3 locks held by swapper/1/0: [ 0.372274] #0: 900000000c9f5e60 (&pcp->lock){+.+.}-{3:3}, at: get_page_from_freelist+0x524/0x1c60 [ 0.372294] #1: 90000000087013b8 (rcu_read_lock){....}-{1:3}, at: rt_spin_trylock+0x50/0x140 [ 0.372305] #2: 900000047fffd388 (&zone->lock){+.+.}-{3:3}, at: __rmqueue_pcplist+0x30c/0xea0 [ 0.372314] irq event stamp: 0 [ 0.372316] hardirqs last enabled at (0): [<0000000000000000>] 0x0 [ 0.372322] hardirqs last disabled at (0): [<9000000005947320>] copy_process+0x9c0/0x26e0 [ 0.372329] softirqs last enabled at (0): [<9000000005947320>] copy_process+0x9c0/0x26e0 [ 0.372335] softirqs last disabled at (0): [<0000000000000000>] 0x0 [ 0.372341] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.12.0-rc7+ #1891 [ 0.372346] Hardware name: Loongson Loongson-3A5000-7A1000-1w-CRB/Loongson-LS3A5000-7A1000-1w-CRB, BIOS vUDK2018-LoongArch-V2.0.0-prebeta9 10/21/2022 [ 0.372349] Stack : 0000000000000089 9000000005a0db9c 90000000071519c8 9000000100388000 [ 0.372486] 900000010038b890 0000000000000000 900000010038b898 9000000007e53788 [ 0.372492] 900000000815bcc8 900000000815bcc0 900000010038b700 0000000000000001 [ 0.372498] 0000000000000001 4b031894b9d6b725 00000000055ec000 9000000100338fc0 [ 0.372503] 00000000000000c4 0000000000000001 000000000000002d 0000000000000003 [ 0.372509] 0000000000000030 0000000000000003 00000000055ec000 0000000000000003 [ 0.372515] 900000000806d000 9000000007e53788 00000000000000b0 0000000000000004 [ 0.372521] 0000000000000000 0000000000000000 900000000c9f5f10 0000000000000000 [ 0.372526] 90000000076f12d8 9000000007e53788 9000000005924778 0000000000000000 [ 0.372532] 00000000000000b0 0000000000000004 0000000000000000 0000000000070000 [ 0.372537] ... [ 0.372540] Call Trace: [ 0.372542] [<9000000005924778>] show_stack+0x38/0x180 [ 0.372548] [<90000000071519c4>] dump_stack_lvl+0x94/0xe4 [ 0.372555] [<900000000599b880>] __might_resched+0x1a0/0x260 [ 0.372561] [<90000000071675cc>] rt_spin_lock+0x4c/0x140 [ 0.372565] [<9000000005cbb768>] __rmqueue_pcplist+0x308/0xea0 [ 0.372570] [<9000000005cbed84>] get_page_from_freelist+0x564/0x1c60 [ 0.372575] [<9000000005cc0d98>] __alloc_pages_noprof+0x218/0x1820 [ 0.372580] [<900000000593b36c>] tlb_init+0x1ac/0x298 [ 0.372585] [<9000000005924b74>] per_cpu_trap_init+0x114/0x140 [ 0.372589] [<9000000005921964>] cpu_probe+0x4e4/0xa60 [ 0.372592] [<9000000005934874>] start_secondary+0x34/0xc0 [ 0.372599] [<900000000715615c>] smpboot_entry+0x64/0x6c

This is because in PREEMPT_RT kernels normal spinlocks are replaced by rt spinlocks and rt_spin_lock() will cause sleeping. Fix it by disabling NUMA optimization completely for PREEMPT_RT kernels.(CVE-2024-56585)

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

f2fs: fix f2fs_bug_on when uninstalling filesystem call f2fs_evict_inode.

creating a large files during checkpoint disable until it runs out of space and then delete it, then remount to enable checkpoint again, and then unmount the filesystem triggers the f2fs_bug_on as below:

------------[ cut here ]------------ kernel BUG at fs/f2fs/inode.c:896! CPU: 2 UID: 0 PID: 1286 Comm: umount Not tainted 6.11.0-rc7-dirty #360 Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI RIP: 0010:f2fs_evict_inode+0x58c/0x610 Call Trace: __die_body+0x15/0x60 die+0x33/0x50 do_trap+0x10a/0x120 f2fs_evict_inode+0x58c/0x610 do_error_trap+0x60/0x80 f2fs_evict_inode+0x58c/0x610 exc_invalid_op+0x53/0x60 f2fs_evict_inode+0x58c/0x610 asm_exc_invalid_op+0x16/0x20 f2fs_evict_inode+0x58c/0x610 evict+0x101/0x260 dispose_list+0x30/0x50 evict_inodes+0x140/0x190 generic_shutdown_super+0x2f/0x150 kill_block_super+0x11/0x40 kill_f2fs_super+0x7d/0x140 deactivate_locked_super+0x2a/0x70 cleanup_mnt+0xb3/0x140 task_work_run+0x61/0x90

The root cause is: creating large files during disable checkpoint period results in not enough free segments, so when writing back root inode will failed in f2fs_enable_checkpoint. When umount the file system after enabling checkpoint, the root inode is dirty in f2fs_evict_inode function, which triggers BUG_ON. The steps to reproduce are as follows:

dd if=/dev/zero of=f2fs.img bs=1M count=55 mount f2fs.img f2fs_dir -o checkpoint=disable:10% dd if=/dev/zero of=big bs=1M count=50 sync rm big mount -o remount,checkpoint=enable f2fs_dir umount f2fs_dir

Let's redirty inode when there is not free segments during checkpoint is disable.(CVE-2024-56586)

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

bpf: Call free_htab_elem() after htab_unlock_bucket()

For htab of maps, when the map is removed from the htab, it may hold the last reference of the map. bpf_map_fd_put_ptr() will invoke bpf_map_free_id() to free the id of the removed map element. However, bpf_map_fd_put_ptr() is invoked while holding a bucket lock (raw_spin_lock_t), and bpf_map_free_id() attempts to acquire map_idr_lock (spinlock_t), triggering the following lockdep warning:

============================= [ BUG: Invalid wait context ] 6.11.0-rc4+ #49 Not tainted

test_maps/4881 is trying to lock: ffffffff84884578 (map_idr_lock){+...}-{3:3}, at: bpf_map_free_id.part.0+0x21/0x70 other info that might help us debug this: context-{5:5} 2 locks held by test_maps/4881: #0: ffffffff846caf60 (rcu_read_lock){....}-{1:3}, at: bpf_fd_htab_map_update_elem+0xf9/0x270 #1: ffff888149ced148 (&htab->lockdep_key#2){....}-{2:2}, at: htab_map_update_elem+0x178/0xa80 stack backtrace: CPU: 0 UID: 0 PID: 4881 Comm: test_maps Not tainted 6.11.0-rc4+ #49 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), ... Call Trace: <TASK> dump_stack_lvl+0x6e/0xb0 dump_stack+0x10/0x20 __lock_acquire+0x73e/0x36c0 lock_acquire+0x182/0x450 _raw_spin_lock_irqsave+0x43/0x70 bpf_map_free_id.part.0+0x21/0x70 bpf_map_put+0xcf/0x110 bpf_map_fd_put_ptr+0x9a/0xb0 free_htab_elem+0x69/0xe0 htab_map_update_elem+0x50f/0xa80 bpf_fd_htab_map_update_elem+0x131/0x270 htab_map_update_elem+0x50f/0xa80 bpf_fd_htab_map_update_elem+0x131/0x270 bpf_map_update_value+0x266/0x380 __sys_bpf+0x21bb/0x36b0 __x64_sys_bpf+0x45/0x60 x64_sys_call+0x1b2a/0x20d0 do_syscall_64+0x5d/0x100 entry_SYSCALL_64_after_hwframe+0x76/0x7e

One way to fix the lockdep warning is using raw_spinlock_t for map_idr_lock as well. However, bpf_map_alloc_id() invokes idr_alloc_cyclic() after acquiring map_idr_lock, it will trigger a similar lockdep warning because the slab's lock (s->cpu_slab->lock) is still a spinlock.

Instead of changing map_idr_lock's type, fix the issue by invoking htab_put_fd_value() after htab_unlock_bucket(). However, only deferring the invocation of htab_put_fd_value() is not enough, because the old map pointers in htab of maps can not be saved during batched deletion. Therefore, also defer the invocation of free_htab_elem(), so these to-be-freed elements could be linked together similar to lru map.

There are four callers for ->map_fd_put_ptr:

(1) alloc_htab_elem() (through htab_put_fd_value()) It invokes ->map_fd_put_ptr() under a raw_spinlock_t. The invocation of htab_put_fd_value() can not simply move after htab_unlock_bucket(), because the old element has already been stashed in htab->extra_elems. It may be reused immediately after htab_unlock_bucket() and the invocation of htab_put_fd_value() after htab_unlock_bucket() may release the newly-added element incorrectly. Therefore, saving the map pointer of the old element for htab of maps before unlocking the bucket and releasing the map_ptr after unlock. Beside the map pointer in the old element, should do the same thing for the special fields in the old element as well.

(2) free_htab_elem() (through htab_put_fd_value()) Its caller includes __htab_map_lookup_and_delete_elem(), htab_map_delete_elem() and __htab_map_lookup_and_delete_batch().

For htab_map_delete_elem(), simply invoke free_htab_elem() after htab_unlock_bucket(). For __htab_map_lookup_and_delete_batch(), just like lru map, linking the to-be-freed element into node_to_free list and invoking free_htab_elem() for these element after unlock. It is safe to reuse batch_flink as the link for node_to_free, because these elements have been removed from the hash llist.

Because htab of maps doesn't support lookup_and_delete operation, __htab_map_lookup_and_delete_elem() doesn't have the problem, so kept it as ---truncated---(CVE-2024-56592)

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

drm/amdgpu: set the right AMDGPU sg segment limitation

The driver needs to set the correct max_segment_size; otherwise debug_dma_map_sg() will complain about the over-mapping of the AMDGPU sg length as following:

WARNING: CPU: 6 PID: 1964 at kernel/dma/debug.c:1178 debug_dma_map_sg+0x2dc/0x370 [ 364.049444] Modules linked in: veth amdgpu(OE) amdxcp drm_exec gpu_sched drm_buddy drm_ttm_helper ttm(OE) drm_suballoc_helper drm_display_helper drm_kms_helper i2c_algo_bit rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace netfs xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo iptable_nat xt_addrtype iptable_filter br_netfilter nvme_fabrics overlay nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge stp llc amd_atl intel_rapl_msr intel_rapl_common sunrpc sch_fq_codel snd_hda_codec_realtek snd_hda_codec_generic snd_hda_scodec_component snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg edac_mce_amd binfmt_misc snd_hda_codec snd_pci_acp6x snd_hda_core snd_acp_config snd_hwdep snd_soc_acpi kvm_amd snd_pcm kvm snd_seq_midi snd_seq_midi_event crct10dif_pclmul ghash_clmulni_intel sha512_ssse3 snd_rawmidi sha256_ssse3 sha1_ssse3 aesni_intel snd_seq nls_iso8859_1 crypto_simd snd_seq_device cryptd snd_timer rapl input_leds snd [ 364.049532] ipmi_devintf wmi_bmof ccp serio_raw k10temp sp5100_tco soundcore ipmi_msghandler cm32181 industrialio mac_hid msr parport_pc ppdev lp parport drm efi_pstore ip_tables x_tables pci_stub crc32_pclmul nvme ahci libahci i2c_piix4 r8169 nvme_core i2c_designware_pci realtek i2c_ccgx_ucsi video wmi hid_generic cdc_ether usbnet usbhid hid r8152 mii [ 364.049576] CPU: 6 PID: 1964 Comm: rocminfo Tainted: G OE 6.10.0-custom #492 [ 364.049579] Hardware name: AMD Majolica-RN/Majolica-RN, BIOS RMJ1009A 06/13/2021 [ 364.049582] RIP: 0010:debug_dma_map_sg+0x2dc/0x370 [ 364.049585] Code: 89 4d b8 e8 36 b1 86 00 8b 4d b8 48 8b 55 b0 44 8b 45 a8 4c 8b 4d a0 48 89 c6 48 c7 c7 00 4b 74 bc 4c 89 4d b8 e8 b4 73 f3 ff <0f> 0b 4c 8b 4d b8 8b 15 c8 2c b8 01 85 d2 0f 85 ee fd ff ff 8b 05 [ 364.049588] RSP: 0018:ffff9ca600b57ac0 EFLAGS: 00010286 [ 364.049590] RAX: 0000000000000000 RBX: ffff88b7c132b0c8 RCX: 0000000000000027 [ 364.049592] RDX: ffff88bb0f521688 RSI: 0000000000000001 RDI: ffff88bb0f521680 [ 364.049594] RBP: ffff9ca600b57b20 R08: 000000000000006f R09: ffff9ca600b57930 [ 364.049596] R10: ffff9ca600b57928 R11: ffffffffbcb46328 R12: 0000000000000000 [ 364.049597] R13: 0000000000000001 R14: ffff88b7c19c0700 R15: ffff88b7c9059800 [ 364.049599] FS: 00007fb2d3516e80(0000) GS:ffff88bb0f500000(0000) knlGS:0000000000000000 [ 364.049601] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 364.049603] CR2: 000055610bd03598 CR3: 00000001049f6000 CR4: 0000000000350ef0 [ 364.049605] Call Trace: [ 364.049607] <TASK> [ 364.049609] ? show_regs+0x6d/0x80 [ 364.049614] ? __warn+0x8c/0x140 [ 364.049618] ? debug_dma_map_sg+0x2dc/0x370 [ 364.049621] ? report_bug+0x193/0x1a0 [ 364.049627] ? handle_bug+0x46/0x80 [ 364.049631] ? exc_invalid_op+0x1d/0x80 [ 364.049635] ? asm_exc_invalid_op+0x1f/0x30 [ 364.049642] ? debug_dma_map_sg+0x2dc/0x370 [ 364.049647] __dma_map_sg_attrs+0x90/0xe0 [ 364.049651] dma_map_sgtable+0x25/0x40 [ 364.049654] amdgpu_bo_move+0x59a/0x850 [amdgpu] [ 364.049935] ? srso_return_thunk+0x5/0x5f [ 364.049939] ? amdgpu_ttm_tt_populate+0x5d/0xc0 [amdgpu] [ 364.050095] ttm_bo_handle_move_mem+0xc3/0x180 [ttm] [ 364.050103] ttm_bo_validate+0xc1/0x160 [ttm] [ 364.050108] ? amdgpu_ttm_tt_get_user_pages+0xe5/0x1b0 [amdgpu] [ 364.050263] amdgpu_amdkfd_gpuvm_alloc_memory_of_gpu+0xa12/0xc90 [amdgpu] [ 364.050473] kfd_ioctl_alloc_memory_of_gpu+0x16b/0x3b0 [amdgpu] [ 364.050680] kfd_ioctl+0x3c2/0x530 [amdgpu] [ 364.050866] ? __pfx_kfd_ioctl_alloc_memory_of_gpu+0x10/0x10 [amdgpu] [ 364.05105 ---truncated---(CVE-2024-56594)

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

jfs: add a check to prevent array-index-out-of-bounds in dbAdjTree

When the value of lp is 0 at the beginning of the for loop, it will become negative in the next assignment and we should bail out.(CVE-2024-56595)

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

jfs: fix array-index-out-of-bounds in jfs_readdir

The stbl might contain some invalid values. Added a check to return error code in that case.(CVE-2024-56596)

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

jfs: fix shift-out-of-bounds in dbSplit

When dmt_budmin is less than zero, it causes errors in the later stages. Added a check to return an error beforehand in dbAllocCtl itself.(CVE-2024-56597)

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

Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create()

bt_sock_alloc() allocates the sk object and attaches it to the provided sock object. On error l2cap_sock_alloc() frees the sk object, but the dangling pointer is still attached to the sock object, which may create use-after-free in other code.(CVE-2024-56605)

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

wifi: rtw88: use ieee80211_purge_tx_queue() to purge TX skb

When removing kernel modules by: rmmod rtw88_8723cs rtw88_8703b rtw88_8723x rtw88_sdio rtw88_core

Driver uses skb_queue_purge() to purge TX skb, but not report tx status causing "Have pending ack frames!" warning. Use ieee80211_purge_tx_queue() to correct this.

Since ieee80211_purge_tx_queue() doesn't take locks, to prevent racing between TX work and purge TX queue, flush and destroy TX work in advance.

wlan0: deauthenticating from aa:f5:fd:60:4c:a8 by local choice (Reason: 3=DEAUTH_LEAVING) ------------[ cut here ]------------ Have pending ack frames! WARNING: CPU: 3 PID: 9232 at net/mac80211/main.c:1691 ieee80211_free_ack_frame+0x5c/0x90 [mac80211] CPU: 3 PID: 9232 Comm: rmmod Tainted: G C 6.10.1-200.fc40.aarch64 #1 Hardware name: pine64 Pine64 PinePhone Braveheart (1.1)/Pine64 PinePhone Braveheart (1.1), BIOS 2024.01 01/01/2024 pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : ieee80211_free_ack_frame+0x5c/0x90 [mac80211] lr : ieee80211_free_ack_frame+0x5c/0x90 [mac80211] sp : ffff80008c1b37b0 x29: ffff80008c1b37b0 x28: ffff000003be8000 x27: 0000000000000000 x26: 0000000000000000 x25: ffff000003dc14b8 x24: ffff80008c1b37d0 x23: ffff000000ff9f80 x22: 0000000000000000 x21: 000000007fffffff x20: ffff80007c7e93d8 x19: ffff00006e66f400 x18: 0000000000000000 x17: ffff7ffffd2b3000 x16: ffff800083fc0000 x15: 0000000000000000 x14: 0000000000000000 x13: 2173656d61726620 x12: 6b636120676e6964 x11: 0000000000000000 x10: 000000000000005d x9 : ffff8000802af2b0 x8 : ffff80008c1b3430 x7 : 0000000000000001 x6 : 0000000000000001 x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000003be8000 Call trace: ieee80211_free_ack_frame+0x5c/0x90 [mac80211] idr_for_each+0x74/0x110 ieee80211_free_hw+0x44/0xe8 [mac80211] rtw_sdio_remove+0x9c/0xc0 [rtw88_sdio] sdio_bus_remove+0x44/0x180 device_remove+0x54/0x90 device_release_driver_internal+0x1d4/0x238 driver_detach+0x54/0xc0 bus_remove_driver+0x78/0x108 driver_unregister+0x38/0x78 sdio_unregister_driver+0x2c/0x40 rtw_8723cs_driver_exit+0x18/0x1000 [rtw88_8723cs] __do_sys_delete_module.isra.0+0x190/0x338 __arm64_sys_delete_module+0x1c/0x30 invoke_syscall+0x74/0x100 el0_svc_common.constprop.0+0x48/0xf0 do_el0_svc+0x24/0x38 el0_svc+0x3c/0x158 el0t_64_sync_handler+0x120/0x138 el0t_64_sync+0x194/0x198 ---[ end trace 0000000000000000 ]---(CVE-2024-56609)

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

sched/numa: fix memory leak due to the overwritten vma->numab_state

[Problem Description] When running the hackbench program of LTP, the following memory leak is reported by kmemleak.

# /opt/ltp/testcases/bin/hackbench 20 thread 1000 Running with 20*40 (== 800) tasks.

# dmesg | grep kmemleak ... kmemleak: 480 new suspected memory leaks (see /sys/kernel/debug/kmemleak) kmemleak: 665 new suspected memory leaks (see /sys/kernel/debug/kmemleak)

# cat /sys/kernel/debug/kmemleak unreferenced object 0xffff888cd8ca2c40 (size 64): comm "hackbench", pid 17142, jiffies 4299780315 hex dump (first 32 bytes): ac 74 49 00 01 00 00 00 4c 84 49 00 01 00 00 00 .tI.....L.I..... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc bff18fd4): [<ffffffff81419a89>] __kmalloc_cache_noprof+0x2f9/0x3f0 [<ffffffff8113f715>] task_numa_work+0x725/0xa00 [<ffffffff8110f878>] task_work_run+0x58/0x90 [<ffffffff81ddd9f8>] syscall_exit_to_user_mode+0x1c8/0x1e0 [<ffffffff81dd78d5>] do_syscall_64+0x85/0x150 [<ffffffff81e0012b>] entry_SYSCALL_64_after_hwframe+0x76/0x7e ...

This issue can be consistently reproduced on three different servers: * a 448-core server * a 256-core server * a 192-core server

[Root Cause] Since multiple threads are created by the hackbench program (along with the command argument 'thread'), a shared vma might be accessed by two or more cores simultaneously. When two or more cores observe that vma->numab_state is NULL at the same time, vma->numab_state will be overwritten.

Although current code ensures that only one thread scans the VMAs in a single 'numa_scan_period', there might be a chance for another thread to enter in the next 'numa_scan_period' while we have not gotten till numab_state allocation [1].

Note that the command /opt/ltp/testcases/bin/hackbench 50 process 1000 cannot the reproduce the issue. It is verified with 200+ test runs.

[Solution] Use the cmpxchg atomic operation to ensure that only one thread executes the vma->numab_state assignment.

[1] https://lore.kernel.org/lkml/1794be3c-358c-4cdc-a43d-a1f841d91ef7@amd.com/(CVE-2024-56613)

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

nilfs2: fix potential out-of-bounds memory access in nilfs_find_entry()

Syzbot reported that when searching for records in a directory where the inode's i_size is corrupted and has a large value, memory access outside the folio/page range may occur, or a use-after-free bug may be detected if KASAN is enabled.

This is because nilfs_last_byte(), which is called by nilfs_find_entry() and others to calculate the number of valid bytes of directory data in a page from i_size and the page index, loses the upper 32 bits of the 64-bit size information due to an inappropriate type of local variable to which the i_size value is assigned.

This caused a large byte offset value due to underflow in the end address calculation in the calling nilfs_find_entry(), resulting in memory access that exceeds the folio/page size.

Fix this issue by changing the type of the local variable causing the bit loss from "unsigned int" to "u64". The return value of nilfs_last_byte() is also of type "unsigned int", but it is truncated so as not to exceed PAGE_SIZE and no bit loss occurs, so no change is required.(CVE-2024-56619)

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

scsi: ufs: core: sysfs: Prevent div by zero

Prevent a division by 0 when monitoring is not enabled.(CVE-2024-56622)

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

ksmbd: fix Out-of-Bounds Write in ksmbd_vfs_stream_write

An offset from client could be a negative value, It could allows to write data outside the bounds of the allocated buffer. Note that this issue is coming when setting 'vfs objects = streams_xattr parameter' in ksmbd.conf..(CVE-2024-56626)

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

scsi: sg: Fix slab-use-after-free read in sg_release()

Fix a use-after-free bug in sg_release(), detected by syzbot with KASAN:

BUG: KASAN: slab-use-after-free in lock_release+0x151/0xa30 kernel/locking/lockdep.c:5838 __mutex_unlock_slowpath+0xe2/0x750 kernel/locking/mutex.c:912 sg_release+0x1f4/0x2e0 drivers/scsi/sg.c:407

In sg_release(), the function kref_put(&sfp->f_ref, sg_remove_sfp) is called before releasing the open_rel_lock mutex. The kref_put() call may decrement the reference count of sfp to zero, triggering its cleanup through sg_remove_sfp(). This cleanup includes scheduling deferred work via sg_remove_sfp_usercontext(), which ultimately frees sfp.

After kref_put(), sg_release() continues to unlock open_rel_lock and may reference sfp or sdp. If sfp has already been freed, this results in a slab-use-after-free error.

Move the kref_put(&sfp->f_ref, sg_remove_sfp) call after unlocking the open_rel_lock mutex. This ensures:

No references to sfp or sdp occur after the reference count is decremented.
Cleanup functions such as sg_remove_sfp() and sg_remove_sfp_usercontext() can safely execute without impacting the mutex handling in sg_release().

The fix has been tested and validated by syzbot. This patch closes the bug reported at the following syzkaller link and ensures proper sequencing of resource cleanup and mutex operations, eliminating the risk of use-after-free errors in sg_release().(CVE-2024-56631)

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

tcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg

The current sk memory accounting logic in __SK_REDIRECT is pre-uncharging tosend bytes, which is either msg->sg.size or a smaller value apply_bytes.

Potential problems with this strategy are as follows:

If the actual sent bytes are smaller than tosend, we need to charge some bytes back, as in line 487, which is okay but seems not clean.
When tosend is set to apply_bytes, as in line 417, and (ret < 0), we may miss uncharging (msg->sg.size - apply_bytes) bytes.

[...] 415 tosend = msg->sg.size; 416 if (psock->apply_bytes && psock->apply_bytes < tosend) 417 tosend = psock->apply_bytes; [...] 443 sk_msg_return(sk, msg, tosend); 444 release_sock(sk); 446 origsize = msg->sg.size; 447 ret = tcp_bpf_sendmsg_redir(sk_redir, redir_ingress, 448 msg, tosend, flags); 449 sent = origsize - msg->sg.size; [...] 454 lock_sock(sk); 455 if (unlikely(ret < 0)) { 456 int free = sk_msg_free_nocharge(sk, msg); 458 if (!cork) 459 *copied -= free; 460 } [...] 487 if (eval == __SK_REDIRECT) 488 sk_mem_charge(sk, tosend - sent); [...]

When running the selftest test_txmsg_redir_wait_sndmem with txmsg_apply, the following warning will be reported:

------------[ cut here ]------------ WARNING: CPU: 6 PID: 57 at net/ipv4/af_inet.c:156 inet_sock_destruct+0x190/0x1a0 Modules linked in: CPU: 6 UID: 0 PID: 57 Comm: kworker/6:0 Not tainted 6.12.0-rc1.bm.1-amd64+ #43 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 Workqueue: events sk_psock_destroy RIP: 0010:inet_sock_destruct+0x190/0x1a0 RSP: 0018:ffffad0a8021fe08 EFLAGS: 00010206 RAX: 0000000000000011 RBX: ffff9aab4475b900 RCX: ffff9aab481a0800 RDX: 0000000000000303 RSI: 0000000000000011 RDI: ffff9aab4475b900 RBP: ffff9aab4475b990 R08: 0000000000000000 R09: ffff9aab40050ec0 R10: 0000000000000000 R11: ffff9aae6fdb1d01 R12: ffff9aab49c60400 R13: ffff9aab49c60598 R14: ffff9aab49c60598 R15: dead000000000100 FS: 0000000000000000(0000) GS:ffff9aae6fd80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffec7e47bd8 CR3: 00000001a1a1c004 CR4: 0000000000770ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <TASK> ? __warn+0x89/0x130 ? inet_sock_destruct+0x190/0x1a0 ? report_bug+0xfc/0x1e0 ? handle_bug+0x5c/0xa0 ? exc_invalid_op+0x17/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? inet_sock_destruct+0x190/0x1a0 __sk_destruct+0x25/0x220 sk_psock_destroy+0x2b2/0x310 process_scheduled_works+0xa3/0x3e0 worker_thread+0x117/0x240 ? __pfx_worker_thread+0x10/0x10 kthread+0xcf/0x100 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x31/0x40 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> ---[ end trace 0000000000000000 ]---

In __SK_REDIRECT, a more concise way is delaying the uncharging after sent bytes are finalized, and uncharge this value. When (ret < 0), we shall invoke sk_msg_free.

Same thing happens in case __SK_DROP, when tosend is set to apply_bytes, we may miss uncharging (msg->sg.size - apply_bytes) bytes. The same warning will be reported in selftest.

[...] 468 case __SK_DROP: 469 default: 470 sk_msg_free_partial(sk, msg, tosend); 471 sk_msg_apply_bytes(psock, tosend); 472 *copied -= (tosend + delta); 473 return -EACCES; [...]

So instead of sk_msg_free_partial we can do sk_msg_free here.(CVE-2024-56633)

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

netfilter: nft_inner: incorrect percpu area handling under softirq

Softirq can interrupt ongoing packet from process context that is walking over the percpu area that contains inner header offsets.

Disable bh and perform three checks before restoring the percpu inner header offsets to validate that the percpu area is valid for this skbuff:

1) If the NFT_PKTINFO_INNER_FULL flag is set on, then this skbuff has already been parsed before for inner header fetching to register.

2) Validate that the percpu area refers to this skbuff using the skbuff pointer as a cookie. If there is a cookie mismatch, then this skbuff needs to be parsed again.

3) Finally, validate if the percpu area refers to this tunnel type.

Only after these three checks the percpu area is restored to a on-stack copy and bh is enabled again.

After inner header fetching, the on-stack copy is stored back to the percpu area.(CVE-2024-56638)

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

net: enetc: Do not configure preemptible TCs if SIs do not support

Both ENETC PF and VF drivers share enetc_setup_tc_mqprio() to configure MQPRIO. And enetc_setup_tc_mqprio() calls enetc_change_preemptible_tcs() to configure preemptible TCs. However, only PF is able to configure preemptible TCs. Because only PF has related registers, while VF does not have these registers. So for VF, its hw->port pointer is NULL. Therefore, VF will access an invalid pointer when accessing a non-existent register, which will cause a crash issue. The simplified log is as follows.

root@ls1028ardb:~# tc qdisc add dev eno0vf0 parent root handle 100: \ mqprio num_tc 4 map 0 0 1 1 2 2 3 3 queues 1@0 1@1 1@2 1@3 hw 1 [ 187.290775] Unable to handle kernel paging request at virtual address 0000000000001f00 [ 187.424831] pc : enetc_mm_commit_preemptible_tcs+0x1c4/0x400 [ 187.430518] lr : enetc_mm_commit_preemptible_tcs+0x30c/0x400 [ 187.511140] Call trace: [ 187.513588] enetc_mm_commit_preemptible_tcs+0x1c4/0x400 [ 187.518918] enetc_setup_tc_mqprio+0x180/0x214 [ 187.523374] enetc_vf_setup_tc+0x1c/0x30 [ 187.527306] mqprio_enable_offload+0x144/0x178 [ 187.531766] mqprio_init+0x3ec/0x668 [ 187.535351] qdisc_create+0x15c/0x488 [ 187.539023] tc_modify_qdisc+0x398/0x73c [ 187.542958] rtnetlink_rcv_msg+0x128/0x378 [ 187.547064] netlink_rcv_skb+0x60/0x130 [ 187.550910] rtnetlink_rcv+0x18/0x24 [ 187.554492] netlink_unicast+0x300/0x36c [ 187.558425] netlink_sendmsg+0x1a8/0x420 [ 187.606759] ---[ end trace 0000000000000000 ]---

In addition, some PFs also do not support configuring preemptible TCs, such as eno1 and eno3 on LS1028A. It won't crash like it does for VFs, but we should prevent these PFs from accessing these unimplemented registers.(CVE-2024-56649)

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

Bluetooth: hci_event: Fix using rcu_read_(un)lock while iterating

The usage of rcu_read_(un)lock while inside list_for_each_entry_rcu is not safe since for the most part entries fetched this way shall be treated as rcu_dereference:

Note that the value returned by rcu_dereference() is valid
only within the enclosing RCU read-side critical section [1]_.
For example, the following is **not** legal::

    rcu_read_lock();
    p = rcu_dereference(head.next);
    rcu_read_unlock();
    x = p-&gt;address;  /* BUG!!! */
    rcu_read_lock();
    y = p-&gt;data; /* BUG!!! */
    rcu_read_unlock();(CVE-2024-56654)

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

net/mlx5: DR, prevent potential error pointer dereference

The dr_domain_add_vport_cap() function generally returns NULL on error but sometimes we want it to return ERR_PTR(-EBUSY) so the caller can retry. The problem here is that "ret" can be either -EBUSY or -ENOMEM and if it's and -ENOMEM then the error pointer is propogated back and eventually dereferenced in dr_ste_v0_build_src_gvmi_qpn_tag().(CVE-2024-56660)

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

acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl

Fix an issue detected by syzbot with KASAN:

BUG: KASAN: vmalloc-out-of-bounds in cmd_to_func drivers/acpi/nfit/ core.c:416 [inline] BUG: KASAN: vmalloc-out-of-bounds in acpi_nfit_ctl+0x20e8/0x24a0 drivers/acpi/nfit/core.c:459

The issue occurs in cmd_to_func when the call_pkg->nd_reserved2 array is accessed without verifying that call_pkg points to a buffer that is appropriately sized as a struct nd_cmd_pkg. This can lead to out-of-bounds access and undefined behavior if the buffer does not have sufficient space.

To address this, a check was added in acpi_nfit_ctl() to ensure that buf is not NULL and that buf_len is less than sizeof(*call_pkg) before accessing it. This ensures safe access to the members of call_pkg, including the nd_reserved2 array.(CVE-2024-56662)

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

wifi: nl80211: fix NL80211_ATTR_MLO_LINK_ID off-by-one

Since the netlink attribute range validation provides inclusive checking, the max of attribute NL80211_ATTR_MLO_LINK_ID should be IEEE80211_MLD_MAX_NUM_LINKS - 1 otherwise causing an off-by-one.

One crash stack for demonstration:

BUG: KASAN: wild-memory-access in ieee80211_tx_control_port+0x3b6/0xca0 net/mac80211/tx.c:5939 Read of size 6 at addr 001102080000000c by task fuzzer.386/9508

CPU: 1 PID: 9508 Comm: syz.1.386 Not tainted 6.1.70 #2 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x177/0x231 lib/dump_stack.c:106 print_report+0xe0/0x750 mm/kasan/report.c:398 kasan_report+0x139/0x170 mm/kasan/report.c:495 kasan_check_range+0x287/0x290 mm/kasan/generic.c:189 memcpy+0x25/0x60 mm/kasan/shadow.c:65 ieee80211_tx_control_port+0x3b6/0xca0 net/mac80211/tx.c:5939 rdev_tx_control_port net/wireless/rdev-ops.h:761 [inline] nl80211_tx_control_port+0x7b3/0xc40 net/wireless/nl80211.c:15453 genl_family_rcv_msg_doit+0x22e/0x320 net/netlink/genetlink.c:756 genl_family_rcv_msg net/netlink/genetlink.c:833 [inline] genl_rcv_msg+0x539/0x740 net/netlink/genetlink.c:850 netlink_rcv_skb+0x1de/0x420 net/netlink/af_netlink.c:2508 genl_rcv+0x24/0x40 net/netlink/genetlink.c:861 netlink_unicast_kernel net/netlink/af_netlink.c:1326 [inline] netlink_unicast+0x74b/0x8c0 net/netlink/af_netlink.c:1352 netlink_sendmsg+0x882/0xb90 net/netlink/af_netlink.c:1874 sock_sendmsg_nosec net/socket.c:716 [inline] __sock_sendmsg net/socket.c:728 [inline] _syssendmsg+0x5cc/0x8f0 net/socket.c:2499 _sys_sendmsg+0x21c/0x290 net/socket.c:2553 __sys_sendmsg net/socket.c:2582 [inline] __do_sys_sendmsg net/socket.c:2591 [inline] __se_sys_sendmsg+0x19e/0x270 net/socket.c:2589 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x45/0x90 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x63/0xcd

Update the policy to ensure correct validation.(CVE-2024-56663)

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

drm/i915: Fix NULL pointer dereference in capture_engine

When the intel_context structure contains NULL, it raises a NULL pointer dereference error in drm_info().

(cherry picked from commit 754302a5bc1bd8fd3b7d85c168b0a1af6d4bba4d)(CVE-2024-56667)

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

blk-cgroup: Fix UAF in blkcg_unpin_online()

blkcg_unpin_online() walks up the blkcg hierarchy putting the online pin. To walk up, it uses blkcg_parent(blkcg) but it was calling that after blkcg_destroy_blkgs(blkcg) which could free the blkcg, leading to the following UAF:

================================================================== BUG: KASAN: slab-use-after-free in blkcg_unpin_online+0x15a/0x270 Read of size 8 at addr ffff8881057678c0 by task kworker/9:1/117

CPU: 9 UID: 0 PID: 117 Comm: kworker/9:1 Not tainted 6.13.0-rc1-work-00182-gb8f52214c61a-dirty #48 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS unknown 02/02/2022 Workqueue: cgwb_release cgwb_release_workfn Call Trace: <TASK> dump_stack_lvl+0x27/0x80 print_report+0x151/0x710 kasan_report+0xc0/0x100 blkcg_unpin_online+0x15a/0x270 cgwb_release_workfn+0x194/0x480 process_scheduled_works+0x71b/0xe20 worker_thread+0x82a/0xbd0 kthread+0x242/0x2c0 ret_from_fork+0x33/0x70 ret_from_fork_asm+0x1a/0x30 </TASK> ... Freed by task 1944: kasan_save_track+0x2b/0x70 kasan_save_free_info+0x3c/0x50 __kasan_slab_free+0x33/0x50 kfree+0x10c/0x330 css_free_rwork_fn+0xe6/0xb30 process_scheduled_works+0x71b/0xe20 worker_thread+0x82a/0xbd0 kthread+0x242/0x2c0 ret_from_fork+0x33/0x70 ret_from_fork_asm+0x1a/0x30

Note that the UAF is not easy to trigger as the free path is indirected behind a couple RCU grace periods and a work item execution. I could only trigger it with artifical msleep() injected in blkcg_unpin_online().

Fix it by reading the parent pointer before destroying the blkcg's blkg's.(CVE-2024-56672)

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

octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_common.c

Add error pointer check after calling otx2_mbox_get_rsp().(CVE-2024-56679)

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

mfd: intel_soc_pmic_bxtwc: Use IRQ domain for USB Type-C device

While design wise the idea of converting the driver to use the hierarchy of the IRQ chips is correct, the implementation has (inherited) flaws. This was unveiled when platform_get_irq() had started WARN() on IRQ 0 that is supposed to be a Linux IRQ number (also known as vIRQ).

Rework the driver to respect IRQ domain when creating each MFD device separately, as the domain is not the same for all of them.(CVE-2024-56691)

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

bpf, sockmap: Several fixes to bpf_msg_pop_data

Several fixes to bpf_msg_pop_data, 1. In sk_msg_shift_left, we should put_page 2. if (len == 0), return early is better 3. pop the entire sk_msg (last == msg->sg.size) should be supported 4. Fix for the value of variable "a" 5. In sk_msg_shift_left, after shifting, i has already pointed to the next element. Addtional sk_msg_iter_var_next may result in BUG.(CVE-2024-56720)

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

octeontx2-pf: handle otx2_mbox_get_rsp errors in cn10k.c

Add error pointer check after calling otx2_mbox_get_rsp().(CVE-2024-56726)

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

rtc: check if __rtc_read_time was successful in rtc_timer_do_work()

If the __rtc_read_time call fails,, the struct rtc_time tm; may contain uninitialized data, or an illegal date/time read from the RTC hardware.

When calling rtc_tm_to_ktime later, the result may be a very large value (possibly KTIME_MAX). If there are periodic timers in rtc->timerqueue, they will continually expire, may causing kernel softlockup.(CVE-2024-56739)

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

vfio/mlx5: Fix an unwind issue in mlx5vf_add_migration_pages()

Fix an unwind issue in mlx5vf_add_migration_pages().

If a set of pages is allocated but fails to be added to the SG table, they need to be freed to prevent a memory leak.

Any pages successfully added to the SG table will be freed as part of mlx5vf_free_data_buffer().(CVE-2024-56742)

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

PCI: Fix reset_method_store() memory leak

In reset_method_store(), a string is allocated via kstrndup() and assigned to the local "options". options is then used in with strsep() to find spaces:

while ((name = strsep(&options, " ")) != NULL) {

If there are no remaining spaces, then options is set to NULL by strsep(), so the subsequent kfree(options) doesn't free the memory allocated via kstrndup().

Fix by using a separate tmp_options to iterate with strsep() so options is preserved.(CVE-2024-56745)

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

scsi: qedi: Fix a possible memory leak in qedi_alloc_and_init_sb()

Hook "qedi_ops->common->sb_init = qed_sb_init" does not release the DMA memory sb_virt when it fails. Add dma_free_coherent() to free it. This is the same way as qedr_alloc_mem_sb() and qede_alloc_mem_sb().(CVE-2024-56747)

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

netfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING

In fscache_create_volume(), there is a missing memory barrier between the bit-clearing operation and the wake-up operation. This may cause a situation where, after a wake-up, the bit-clearing operation hasn't been detected yet, leading to an indefinite wait. The triggering process is as follows:

[cookie1] [cookie2] [volume_work] fscache_perform_lookup fscache_create_volume fscache_perform_lookup fscache_create_volume fscache_create_volume_work cachefiles_acquire_volume clear_and_wake_up_bit test_and_set_bit test_and_set_bit goto maybe_wait goto no_wait

In the above process, cookie1 and cookie2 has the same volume. When cookie1 enters the -no_wait- process, it will clear the bit and wake up the waiting process. If a barrier is missing, it may cause cookie2 to remain in the -wait- process indefinitely.

In commit 3288666c7256 ("fscache: Use clear_and_wake_up_bit() in fscache_create_volume_work()"), barriers were added to similar operations in fscache_create_volume_work(), but fscache_create_volume() was missed.

By combining the clear and wake operations into clear_and_wake_up_bit() to fix this issue.(CVE-2024-56755)

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

nvme-pci: fix freeing of the HMB descriptor table

The HMB descriptor table is sized to the maximum number of descriptors that could be used for a given device, but __nvme_alloc_host_mem could break out of the loop earlier on memory allocation failure and end up using less descriptors than planned for, which leads to an incorrect size passed to dma_free_coherent.

In practice this was not showing up because the number of descriptors tends to be low and the dma coherent allocator always allocates and frees at least a page.(CVE-2024-56756)

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

btrfs: fix use-after-free when COWing tree bock and tracing is enabled

When a COWing a tree block, at btrfs_cow_block(), and we have the tracepoint trace_btrfs_cow_block() enabled and preemption is also enabled (CONFIG_PREEMPT=y), we can trigger a use-after-free in the COWed extent buffer while inside the tracepoint code. This is because in some paths that call btrfs_cow_block(), such as btrfs_search_slot(), we are holding the last reference on the extent buffer @buf so btrfs_force_cow_block() drops the last reference on the @buf extent buffer when it calls free_extent_buffer_stale(buf), which schedules the release of the extent buffer with RCU. This means that if we are on a kernel with preemption, the current task may be preempted before calling trace_btrfs_cow_block() and the extent buffer already released by the time trace_btrfs_cow_block() is called, resulting in a use-after-free.

Fix this by moving the trace_btrfs_cow_block() from btrfs_cow_block() to btrfs_force_cow_block() before the COWed extent buffer is freed. This also has a side effect of invoking the tracepoint in the tree defrag code, at defrag.c:btrfs_realloc_node(), since btrfs_force_cow_block() is called there, but this is fine and it was actually missing there.(CVE-2024-56759)

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

tracing: Prevent bad count for tracing_cpumask_write

If a large count is provided, it will trigger a warning in bitmap_parse_user. Also check zero for it.(CVE-2024-56763)

Severity

8.0 (High)


                    
                      CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References

URL

Type

	https://www.openeuler.org/zh/security/security-bu…	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-50191	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53050	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53128	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53150	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53155	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53157	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53158	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53159	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53160	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53171	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53180	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53187	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53190	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53191	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53194	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53196	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53203	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53213	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53215	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53218	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53219	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53224	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53229	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53231	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53234	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53239	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-53241	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-55639	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56543	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56546	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56549	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56562	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56570	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56572	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56582	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56583	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56585	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56586	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56592	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56594	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56595	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56596	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56597	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56605	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56609	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56613	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56619	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56622	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56626	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56631	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56633	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56638	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56649	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56654	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56660	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56662	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56663	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56667	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56672	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56679	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56691	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56720	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56726	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56739	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56742	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56745	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56747	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56755	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56756	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56759	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-56763	ADVISORY

JSON

To clipboard

{
  "affected": [
    {
      "ecosystem_specific": {
        "aarch64": [
          "bpftool-6.6.0-75.0.0.79.oe2403sp1.aarch64.rpm",
          "bpftool-debuginfo-6.6.0-75.0.0.79.oe2403sp1.aarch64.rpm",
          "kernel-6.6.0-75.0.0.79.oe2403sp1.aarch64.rpm",
          "kernel-debuginfo-6.6.0-75.0.0.79.oe2403sp1.aarch64.rpm",
          "kernel-debugsource-6.6.0-75.0.0.79.oe2403sp1.aarch64.rpm",
          "kernel-devel-6.6.0-75.0.0.79.oe2403sp1.aarch64.rpm",
          "kernel-headers-6.6.0-75.0.0.79.oe2403sp1.aarch64.rpm",
          "kernel-source-6.6.0-75.0.0.79.oe2403sp1.aarch64.rpm",
          "kernel-tools-6.6.0-75.0.0.79.oe2403sp1.aarch64.rpm",
          "kernel-tools-debuginfo-6.6.0-75.0.0.79.oe2403sp1.aarch64.rpm",
          "kernel-tools-devel-6.6.0-75.0.0.79.oe2403sp1.aarch64.rpm",
          "perf-6.6.0-75.0.0.79.oe2403sp1.aarch64.rpm",
          "perf-debuginfo-6.6.0-75.0.0.79.oe2403sp1.aarch64.rpm",
          "python3-perf-6.6.0-75.0.0.79.oe2403sp1.aarch64.rpm",
          "python3-perf-debuginfo-6.6.0-75.0.0.79.oe2403sp1.aarch64.rpm"
        ],
        "src": [
          "kernel-6.6.0-75.0.0.79.oe2403sp1.src.rpm"
        ],
        "x86_64": [
          "bpftool-6.6.0-75.0.0.79.oe2403sp1.x86_64.rpm",
          "bpftool-debuginfo-6.6.0-75.0.0.79.oe2403sp1.x86_64.rpm",
          "kernel-6.6.0-75.0.0.79.oe2403sp1.x86_64.rpm",
          "kernel-debuginfo-6.6.0-75.0.0.79.oe2403sp1.x86_64.rpm",
          "kernel-debugsource-6.6.0-75.0.0.79.oe2403sp1.x86_64.rpm",
          "kernel-devel-6.6.0-75.0.0.79.oe2403sp1.x86_64.rpm",
          "kernel-headers-6.6.0-75.0.0.79.oe2403sp1.x86_64.rpm",
          "kernel-source-6.6.0-75.0.0.79.oe2403sp1.x86_64.rpm",
          "kernel-tools-6.6.0-75.0.0.79.oe2403sp1.x86_64.rpm",
          "kernel-tools-debuginfo-6.6.0-75.0.0.79.oe2403sp1.x86_64.rpm",
          "kernel-tools-devel-6.6.0-75.0.0.79.oe2403sp1.x86_64.rpm",
          "perf-6.6.0-75.0.0.79.oe2403sp1.x86_64.rpm",
          "perf-debuginfo-6.6.0-75.0.0.79.oe2403sp1.x86_64.rpm",
          "python3-perf-6.6.0-75.0.0.79.oe2403sp1.x86_64.rpm",
          "python3-perf-debuginfo-6.6.0-75.0.0.79.oe2403sp1.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:24.03-LTS-SP1",
        "name": "kernel",
        "purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-24.03-LTS-SP1"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.6.0-75.0.0.79.oe2403sp1"
            }
          ],
          "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\next4: don\u0026apos;t set SB_RDONLY after filesystem errors\n\nWhen the filesystem is mounted with errors=remount-ro, we were setting\nSB_RDONLY flag to stop all filesystem modifications. We knew this misses\nproper locking (sb-\u0026gt;s_umount) and does not go through proper filesystem\nremount procedure but it has been the way this worked since early ext2\ndays and it was good enough for catastrophic situation damage\nmitigation. Recently, syzbot has found a way (see link) to trigger\nwarnings in filesystem freezing because the code got confused by\nSB_RDONLY changing under its hands. Since these days we set\nEXT4_FLAGS_SHUTDOWN on the superblock which is enough to stop all\nfilesystem modifications, modifying SB_RDONLY shouldn\u0026apos;t be needed. So\nstop doing that.(CVE-2024-50191)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915/hdcp: Add encoder check in hdcp2_get_capability\n\nAdd encoder check in intel_hdcp2_get_capability to avoid\nnull pointer error.(CVE-2024-53050)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/task_stack: fix object_is_on_stack() for KASAN tagged pointers\n\nWhen CONFIG_KASAN_SW_TAGS and CONFIG_KASAN_STACK are enabled, the\nobject_is_on_stack() function may produce incorrect results due to the\npresence of tags in the obj pointer, while the stack pointer does not have\ntags.  This discrepancy can lead to incorrect stack object detection and\nsubsequently trigger warnings if CONFIG_DEBUG_OBJECTS is also enabled.\n\nExample of the warning:\n\nODEBUG: object 3eff800082ea7bb0 is NOT on stack ffff800082ea0000, but annotated.\n------------[ cut here ]------------\nWARNING: CPU: 0 PID: 1 at lib/debugobjects.c:557 __debug_object_init+0x330/0x364\nModules linked in:\nCPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.0-rc5 #4\nHardware name: linux,dummy-virt (DT)\npstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : __debug_object_init+0x330/0x364\nlr : __debug_object_init+0x330/0x364\nsp : ffff800082ea7b40\nx29: ffff800082ea7b40 x28: 98ff0000c0164518 x27: 98ff0000c0164534\nx26: ffff800082d93ec8 x25: 0000000000000001 x24: 1cff0000c00172a0\nx23: 0000000000000000 x22: ffff800082d93ed0 x21: ffff800081a24418\nx20: 3eff800082ea7bb0 x19: efff800000000000 x18: 0000000000000000\nx17: 00000000000000ff x16: 0000000000000047 x15: 206b63617473206e\nx14: 0000000000000018 x13: ffff800082ea7780 x12: 0ffff800082ea78e\nx11: 0ffff800082ea790 x10: 0ffff800082ea79d x9 : 34d77febe173e800\nx8 : 34d77febe173e800 x7 : 0000000000000001 x6 : 0000000000000001\nx5 : feff800082ea74b8 x4 : ffff800082870a90 x3 : ffff80008018d3c4\nx2 : 0000000000000001 x1 : ffff800082858810 x0 : 0000000000000050\nCall trace:\n __debug_object_init+0x330/0x364\n debug_object_init_on_stack+0x30/0x3c\n schedule_hrtimeout_range_clock+0xac/0x26c\n schedule_hrtimeout+0x1c/0x30\n wait_task_inactive+0x1d4/0x25c\n kthread_bind_mask+0x28/0x98\n init_rescuer+0x1e8/0x280\n workqueue_init+0x1a0/0x3cc\n kernel_init_freeable+0x118/0x200\n kernel_init+0x28/0x1f0\n ret_from_fork+0x10/0x20\n---[ end trace 0000000000000000 ]---\nODEBUG: object 3eff800082ea7bb0 is NOT on stack ffff800082ea0000, but annotated.\n------------[ cut here ]------------(CVE-2024-53128)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nALSA: usb-audio: Fix out of bounds reads when finding clock sources\n\nThe current USB-audio driver code doesn\u0026apos;t check bLength of each\ndescriptor at traversing for clock descriptors.  That is, when a\ndevice provides a bogus descriptor with a shorter bLength, the driver\nmight hit out-of-bounds reads.\n\nFor addressing it, this patch adds sanity checks to the validator\nfunctions for the clock descriptor traversal.  When the descriptor\nlength is shorter than expected, it\u0026apos;s skipped in the loop.\n\nFor the clock source and clock multiplier descriptors, we can just\ncheck bLength against the sizeof() of each descriptor type.\nOTOH, the clock selector descriptor of UAC2 and UAC3 has an array\nof bNrInPins elements and two more fields at its tail, hence those\nhave to be checked in addition to the sizeof() check.(CVE-2024-53150)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: fix uninitialized value in ocfs2_file_read_iter()\n\nSyzbot has reported the following KMSAN splat:\n\nBUG: KMSAN: uninit-value in ocfs2_file_read_iter+0x9a4/0xf80\n ocfs2_file_read_iter+0x9a4/0xf80\n __io_read+0x8d4/0x20f0\n io_read+0x3e/0xf0\n io_issue_sqe+0x42b/0x22c0\n io_wq_submit_work+0xaf9/0xdc0\n io_worker_handle_work+0xd13/0x2110\n io_wq_worker+0x447/0x1410\n ret_from_fork+0x6f/0x90\n ret_from_fork_asm+0x1a/0x30\n\nUninit was created at:\n __alloc_pages_noprof+0x9a7/0xe00\n alloc_pages_mpol_noprof+0x299/0x990\n alloc_pages_noprof+0x1bf/0x1e0\n allocate_slab+0x33a/0x1250\n ___slab_alloc+0x12ef/0x35e0\n kmem_cache_alloc_bulk_noprof+0x486/0x1330\n __io_alloc_req_refill+0x84/0x560\n io_submit_sqes+0x172f/0x2f30\n __se_sys_io_uring_enter+0x406/0x41c0\n __x64_sys_io_uring_enter+0x11f/0x1a0\n x64_sys_call+0x2b54/0x3ba0\n do_syscall_64+0xcd/0x1e0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nSince an instance of \u0026apos;struct kiocb\u0026apos; may be passed from the block layer\nwith \u0026apos;private\u0026apos; field uninitialized, introduce \u0026apos;ocfs2_iocb_init_rw_locked()\u0026apos;\nand use it from where \u0026apos;ocfs2_dio_end_io()\u0026apos; might take care, i.e. in\n\u0026apos;ocfs2_file_read_iter()\u0026apos; and \u0026apos;ocfs2_file_write_iter()\u0026apos;.(CVE-2024-53155)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_scpi: Check the DVFS OPP count returned by the firmware\n\nFix a kernel crash with the below call trace when the SCPI firmware\nreturns OPP count of zero.\n\ndvfs_info.opp_count may be zero on some platforms during the reboot\ntest, and the kernel will crash after dereferencing the pointer to\nkcalloc(info-\u0026gt;count, sizeof(*opp), GFP_KERNEL).\n\n  |  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000028\n  |  Mem abort info:\n  |    ESR = 0x96000004\n  |    Exception class = DABT (current EL), IL = 32 bits\n  |    SET = 0, FnV = 0\n  |    EA = 0, S1PTW = 0\n  |  Data abort info:\n  |    ISV = 0, ISS = 0x00000004\n  |    CM = 0, WnR = 0\n  |  user pgtable: 4k pages, 48-bit VAs, pgdp = 00000000faefa08c\n  |  [0000000000000028] pgd=0000000000000000\n  |  Internal error: Oops: 96000004 [#1] SMP\n  |  scpi-hwmon: probe of PHYT000D:00 failed with error -110\n  |  Process systemd-udevd (pid: 1701, stack limit = 0x00000000aaede86c)\n  |  CPU: 2 PID: 1701 Comm: systemd-udevd Not tainted 4.19.90+ #1\n  |  Hardware name: PHYTIUM LTD Phytium FT2000/4/Phytium FT2000/4, BIOS\n  |  pstate: 60000005 (nZCv daif -PAN -UAO)\n  |  pc : scpi_dvfs_recalc_rate+0x40/0x58 [clk_scpi]\n  |  lr : clk_register+0x438/0x720\n  |  Call trace:\n  |   scpi_dvfs_recalc_rate+0x40/0x58 [clk_scpi]\n  |   devm_clk_hw_register+0x50/0xa0\n  |   scpi_clk_ops_init.isra.2+0xa0/0x138 [clk_scpi]\n  |   scpi_clocks_probe+0x528/0x70c [clk_scpi]\n  |   platform_drv_probe+0x58/0xa8\n  |   really_probe+0x260/0x3d0\n  |   driver_probe_device+0x12c/0x148\n  |   device_driver_attach+0x74/0x98\n  |   __driver_attach+0xb4/0xe8\n  |   bus_for_each_dev+0x88/0xe0\n  |   driver_attach+0x30/0x40\n  |   bus_add_driver+0x178/0x2b0\n  |   driver_register+0x64/0x118\n  |   __platform_driver_register+0x54/0x60\n  |   scpi_clocks_driver_init+0x24/0x1000 [clk_scpi]\n  |   do_one_initcall+0x54/0x220\n  |   do_init_module+0x54/0x1c8\n  |   load_module+0x14a4/0x1668\n  |   __se_sys_finit_module+0xf8/0x110\n  |   __arm64_sys_finit_module+0x24/0x30\n  |   el0_svc_common+0x78/0x170\n  |   el0_svc_handler+0x38/0x78\n  |   el0_svc+0x8/0x340\n  |  Code: 937d7c00 a94153f3 a8c27bfd f9400421 (b8606820)\n  |  ---[ end trace 06feb22469d89fa8 ]---\n  |  Kernel panic - not syncing: Fatal exception\n  |  SMP: stopping secondary CPUs\n  |  Kernel Offset: disabled\n  |  CPU features: 0x10,a0002008\n  |  Memory Limit: none(CVE-2024-53157)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsoc: qcom: geni-se: fix array underflow in geni_se_clk_tbl_get()\n\nThis loop is supposed to break if the frequency returned from\nclk_round_rate() is the same as on the previous iteration.  However,\nthat check doesn\u0026apos;t make sense on the first iteration through the loop.\nIt leads to reading before the start of these-\u0026gt;clk_perf_tbl[] array.(CVE-2024-53158)\n\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2024-53159)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nrcu/kvfree: Fix data-race in __mod_timer / kvfree_call_rcu\n\nKCSAN reports a data race when access the krcp-\u0026gt;monitor_work.timer.expires\nvariable in the schedule_delayed_monitor_work() function:\n\n\u0026lt;snip\u0026gt;\nBUG: KCSAN: data-race in __mod_timer / kvfree_call_rcu\n\nread to 0xffff888237d1cce8 of 8 bytes by task 10149 on cpu 1:\n schedule_delayed_monitor_work kernel/rcu/tree.c:3520 [inline]\n kvfree_call_rcu+0x3b8/0x510 kernel/rcu/tree.c:3839\n trie_update_elem+0x47c/0x620 kernel/bpf/lpm_trie.c:441\n bpf_map_update_value+0x324/0x350 kernel/bpf/syscall.c:203\n generic_map_update_batch+0x401/0x520 kernel/bpf/syscall.c:1849\n bpf_map_do_batch+0x28c/0x3f0 kernel/bpf/syscall.c:5143\n __sys_bpf+0x2e5/0x7a0\n __do_sys_bpf kernel/bpf/syscall.c:5741 [inline]\n __se_sys_bpf kernel/bpf/syscall.c:5739 [inline]\n __x64_sys_bpf+0x43/0x50 kernel/bpf/syscall.c:5739\n x64_sys_call+0x2625/0x2d60 arch/x86/include/generated/asm/syscalls_64.h:322\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nwrite to 0xffff888237d1cce8 of 8 bytes by task 56 on cpu 0:\n __mod_timer+0x578/0x7f0 kernel/time/timer.c:1173\n add_timer_global+0x51/0x70 kernel/time/timer.c:1330\n __queue_delayed_work+0x127/0x1a0 kernel/workqueue.c:2523\n queue_delayed_work_on+0xdf/0x190 kernel/workqueue.c:2552\n queue_delayed_work include/linux/workqueue.h:677 [inline]\n schedule_delayed_monitor_work kernel/rcu/tree.c:3525 [inline]\n kfree_rcu_monitor+0x5e8/0x660 kernel/rcu/tree.c:3643\n process_one_work kernel/workqueue.c:3229 [inline]\n process_scheduled_works+0x483/0x9a0 kernel/workqueue.c:3310\n worker_thread+0x51d/0x6f0 kernel/workqueue.c:3391\n kthread+0x1d1/0x210 kernel/kthread.c:389\n ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244\n\nReported by Kernel Concurrency Sanitizer on:\nCPU: 0 UID: 0 PID: 56 Comm: kworker/u8:4 Not tainted 6.12.0-rc2-syzkaller-00050-g5b7c893ed5ed #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024\nWorkqueue: events_unbound kfree_rcu_monitor\n\u0026lt;snip\u0026gt;\n\nkfree_rcu_monitor() rearms the work if a \u0026quot;krcp\u0026quot; has to be still\noffloaded and this is done without holding krcp-\u0026gt;lock, whereas\nthe kvfree_call_rcu() holds it.\n\nFix it by acquiring the \u0026quot;krcp-\u0026gt;lock\u0026quot; for kfree_rcu_monitor() so\nboth functions do not race anymore.(CVE-2024-53160)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit\n\nAfter an insertion in TNC, the tree might split and cause a node to\nchange its `znode-\u0026gt;parent`. A further deletion of other nodes in the\ntree (which also could free the nodes), the aforementioned node\u0026apos;s\n`znode-\u0026gt;cparent` could still point to a freed node. This\n`znode-\u0026gt;cparent` may not be updated when getting nodes to commit in\n`ubifs_tnc_start_commit()`. This could then trigger a use-after-free\nwhen accessing the `znode-\u0026gt;cparent` in `write_index()` in\n`ubifs_tnc_end_commit()`.\n\nThis can be triggered by running\n\n  rm -f /etc/test-file.bin\n  dd if=/dev/urandom of=/etc/test-file.bin bs=1M count=60 conv=fsync\n\nin a loop, and with `CONFIG_UBIFS_FS_AUTHENTICATION`. KASAN then\nreports:\n\n  BUG: KASAN: use-after-free in ubifs_tnc_end_commit+0xa5c/0x1950\n  Write of size 32 at addr ffffff800a3af86c by task ubifs_bgt0_20/153\n\n  Call trace:\n   dump_backtrace+0x0/0x340\n   show_stack+0x18/0x24\n   dump_stack_lvl+0x9c/0xbc\n   print_address_description.constprop.0+0x74/0x2b0\n   kasan_report+0x1d8/0x1f0\n   kasan_check_range+0xf8/0x1a0\n   memcpy+0x84/0xf4\n   ubifs_tnc_end_commit+0xa5c/0x1950\n   do_commit+0x4e0/0x1340\n   ubifs_bg_thread+0x234/0x2e0\n   kthread+0x36c/0x410\n   ret_from_fork+0x10/0x20\n\n  Allocated by task 401:\n   kasan_save_stack+0x38/0x70\n   __kasan_kmalloc+0x8c/0xd0\n   __kmalloc+0x34c/0x5bc\n   tnc_insert+0x140/0x16a4\n   ubifs_tnc_add+0x370/0x52c\n   ubifs_jnl_write_data+0x5d8/0x870\n   do_writepage+0x36c/0x510\n   ubifs_writepage+0x190/0x4dc\n   __writepage+0x58/0x154\n   write_cache_pages+0x394/0x830\n   do_writepages+0x1f0/0x5b0\n   filemap_fdatawrite_wbc+0x170/0x25c\n   file_write_and_wait_range+0x140/0x190\n   ubifs_fsync+0xe8/0x290\n   vfs_fsync_range+0xc0/0x1e4\n   do_fsync+0x40/0x90\n   __arm64_sys_fsync+0x34/0x50\n   invoke_syscall.constprop.0+0xa8/0x260\n   do_el0_svc+0xc8/0x1f0\n   el0_svc+0x34/0x70\n   el0t_64_sync_handler+0x108/0x114\n   el0t_64_sync+0x1a4/0x1a8\n\n  Freed by task 403:\n   kasan_save_stack+0x38/0x70\n   kasan_set_track+0x28/0x40\n   kasan_set_free_info+0x28/0x4c\n   __kasan_slab_free+0xd4/0x13c\n   kfree+0xc4/0x3a0\n   tnc_delete+0x3f4/0xe40\n   ubifs_tnc_remove_range+0x368/0x73c\n   ubifs_tnc_remove_ino+0x29c/0x2e0\n   ubifs_jnl_delete_inode+0x150/0x260\n   ubifs_evict_inode+0x1d4/0x2e4\n   evict+0x1c8/0x450\n   iput+0x2a0/0x3c4\n   do_unlinkat+0x2cc/0x490\n   __arm64_sys_unlinkat+0x90/0x100\n   invoke_syscall.constprop.0+0xa8/0x260\n   do_el0_svc+0xc8/0x1f0\n   el0_svc+0x34/0x70\n   el0t_64_sync_handler+0x108/0x114\n   el0t_64_sync+0x1a4/0x1a8\n\nThe offending `memcpy()` in `ubifs_copy_hash()` has a use-after-free\nwhen a node becomes root in TNC but still has a `cparent` to an already\nfreed node. More specifically, consider the following TNC:\n\n         zroot\n         /\n        /\n      zp1\n      /\n     /\n    zn\n\nInserting a new node `zn_new` with a key smaller then `zn` will trigger\na split in `tnc_insert()` if `zp1` is full:\n\n         zroot\n         /   \\\n        /     \\\n      zp1     zp2\n      /         \\\n     /           \\\n  zn_new          zn\n\n`zn-\u0026gt;parent` has now been moved to `zp2`, *but* `zn-\u0026gt;cparent` still\npoints to `zp1`.\n\nNow, consider a removal of all the nodes _except_ `zn`. Just when\n`tnc_delete()` is about to delete `zroot` and `zp2`:\n\n         zroot\n             \\\n              \\\n              zp2\n                \\\n                 \\\n                 zn\n\n`zroot` and `zp2` get freed and the tree collapses:\n\n           zn\n\n`zn` now becomes the new `zroot`.\n\n`get_znodes_to_commit()` will now only find `zn`, the new `zroot`, and\n`write_index()` will check its `znode-\u0026gt;cparent` that wrongly points to\nthe already freed `zp1`. `ubifs_copy_hash()` thus gets wrongly called\nwith `znode-\u0026gt;cparent-\u0026gt;zbranch[znode-\u0026gt;iip].hash` that triggers the\nuse-after-free!\n\nFix this by explicitly setting `znode-\u0026gt;cparent` to `NULL` in\n`get_znodes_to_commit()` for the root node. The search for the dirty\nnodes\n---truncated---(CVE-2024-53171)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nALSA: pcm: Add sanity NULL check for the default mmap fault handler\n\nA driver might allow the mmap access before initializing its\nruntime-\u0026gt;dma_area properly.  Add a proper NULL check before passing to\nvirt_to_page() for avoiding a panic.(CVE-2024-53180)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring: check for overflows in io_pin_pages\n\nWARNING: CPU: 0 PID: 5834 at io_uring/memmap.c:144 io_pin_pages+0x149/0x180 io_uring/memmap.c:144\nCPU: 0 UID: 0 PID: 5834 Comm: syz-executor825 Not tainted 6.12.0-next-20241118-syzkaller #0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __io_uaddr_map+0xfb/0x2d0 io_uring/memmap.c:183\n io_rings_map io_uring/io_uring.c:2611 [inline]\n io_allocate_scq_urings+0x1c0/0x650 io_uring/io_uring.c:3470\n io_uring_create+0x5b5/0xc00 io_uring/io_uring.c:3692\n io_uring_setup io_uring/io_uring.c:3781 [inline]\n ...\n \u0026lt;/TASK\u0026gt;\n\nio_pin_pages()\u0026apos;s uaddr parameter came directly from the user and can be\ngarbage. Don\u0026apos;t just add size to it as it can overflow.(CVE-2024-53187)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtlwifi: Drastically reduce the attempts to read efuse in case of failures\n\nSyzkaller reported a hung task with uevent_show() on stack trace. That\nspecific issue was addressed by another commit [0], but even with that\nfix applied (for example, running v6.12-rc5) we face another type of hung\ntask that comes from the same reproducer [1]. By investigating that, we\ncould narrow it to the following path:\n\n(a) Syzkaller emulates a Realtek USB WiFi adapter using raw-gadget and\ndummy_hcd infrastructure.\n\n(b) During the probe of rtl8192cu, the driver ends-up performing an efuse\nread procedure (which is related to EEPROM load IIUC), and here lies the\nissue: the function read_efuse() calls read_efuse_byte() many times, as\nloop iterations depending on the efuse size (in our example, 512 in total).\n\nThis procedure for reading efuse bytes relies in a loop that performs an\nI/O read up to *10k* times in case of failures. We measured the time of\nthe loop inside read_efuse_byte() alone, and in this reproducer (which\ninvolves the dummy_hcd emulation layer), it takes 15 seconds each. As a\nconsequence, we have the driver stuck in its probe routine for big time,\nexposing a stack trace like below if we attempt to reboot the system, for\nexample:\n\ntask:kworker/0:3 state:D stack:0 pid:662 tgid:662 ppid:2 flags:0x00004000\nWorkqueue: usb_hub_wq hub_event\nCall Trace:\n __schedule+0xe22/0xeb6\n schedule_timeout+0xe7/0x132\n __wait_for_common+0xb5/0x12e\n usb_start_wait_urb+0xc5/0x1ef\n ? usb_alloc_urb+0x95/0xa4\n usb_control_msg+0xff/0x184\n _usbctrl_vendorreq_sync+0xa0/0x161\n _usb_read_sync+0xb3/0xc5\n read_efuse_byte+0x13c/0x146\n read_efuse+0x351/0x5f0\n efuse_read_all_map+0x42/0x52\n rtl_efuse_shadow_map_update+0x60/0xef\n rtl_get_hwinfo+0x5d/0x1c2\n rtl92cu_read_eeprom_info+0x10a/0x8d5\n ? rtl92c_read_chip_version+0x14f/0x17e\n rtl_usb_probe+0x323/0x851\n usb_probe_interface+0x278/0x34b\n really_probe+0x202/0x4a4\n __driver_probe_device+0x166/0x1b2\n driver_probe_device+0x2f/0xd8\n [...]\n\nWe propose hereby to drastically reduce the attempts of doing the I/O\nreads in case of failures, restricted to USB devices (given that\nthey\u0026apos;re inherently slower than PCIe ones). By retrying up to 10 times\n(instead of 10000), we got reponsiveness in the reproducer, while seems\nreasonable to believe that there\u0026apos;s no sane USB device implementation in\nthe field requiring this amount of retries at every I/O read in order\nto properly work. Based on that assumption, it\u0026apos;d be good to have it\nbackported to stable but maybe not since driver implementation (the 10k\nnumber comes from day 0), perhaps up to 6.x series makes sense.\n\n[0] Commit 15fffc6a5624 (\u0026quot;driver core: Fix uevent_show() vs driver detach race\u0026quot;)\n\n[1] A note about that: this syzkaller report presents multiple reproducers\nthat differs by the type of emulated USB device. For this specific case,\ncheck the entry from 2024/08/08 06:23 in the list of crashes; the C repro\nis available at https://syzkaller.appspot.com/text?tag=ReproC\u0026amp;x=1521fc83980000.(CVE-2024-53190)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath12k: fix warning when unbinding\n\nIf there is an error during some initialization related to firmware,\nthe buffers dp-\u0026gt;tx_ring[i].tx_status are released.\nHowever this is released again when the device is unbinded (ath12k_pci),\nand we get:\nWARNING: CPU: 0 PID: 2098 at mm/slub.c:4689 free_large_kmalloc+0x4d/0x80\nCall Trace:\nfree_large_kmalloc\nath12k_dp_free\nath12k_core_deinit\nath12k_pci_remove\n...\n\nThe issue is always reproducible from a VM because the MSI addressing\ninitialization is failing.\n\nIn order to fix the issue, just set the buffers to NULL after releasing in\norder to avoid the double free.(CVE-2024-53191)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: Fix use-after-free of slot-\u0026gt;bus on hot remove\n\nDennis reports a boot crash on recent Lenovo laptops with a USB4 dock.\n\nSince commit 0fc70886569c (\u0026quot;thunderbolt: Reset USB4 v2 host router\u0026quot;) and\ncommit 59a54c5f3dbd (\u0026quot;thunderbolt: Reset topology created by the boot\nfirmware\u0026quot;), USB4 v2 and v1 Host Routers are reset on probe of the\nthunderbolt driver.\n\nThe reset clears the Presence Detect State and Data Link Layer Link Active\nbits at the USB4 Host Router\u0026apos;s Root Port and thus causes hot removal of the\ndock.\n\nThe crash occurs when pciehp is unbound from one of the dock\u0026apos;s Downstream\nPorts:  pciehp creates a pci_slot on bind and destroys it on unbind.  The\npci_slot contains a pointer to the pci_bus below the Downstream Port, but\na reference on that pci_bus is never acquired.  The pci_bus is destroyed\nbefore the pci_slot, so a use-after-free ensues when pci_slot_release()\naccesses slot-\u0026gt;bus.\n\nIn principle this should not happen because pci_stop_bus_device() unbinds\npciehp (and therefore destroys the pci_slot) before the pci_bus is\ndestroyed by pci_remove_bus_device().\n\nHowever the stacktrace provided by Dennis shows that pciehp is unbound from\npci_remove_bus_device() instead of pci_stop_bus_device().  To understand\nthe significance of this, one needs to know that the PCI core uses a two\nstep process to remove a portion of the hierarchy:  It first unbinds all\ndrivers in the sub-hierarchy in pci_stop_bus_device() and then actually\nremoves the devices in pci_remove_bus_device().  There is no precaution to\nprevent driver binding in-between pci_stop_bus_device() and\npci_remove_bus_device().\n\nIn Dennis\u0026apos; case, it seems removal of the hierarchy by pciehp races with\ndriver binding by pci_bus_add_devices().  pciehp is bound to the\nDownstream Port after pci_stop_bus_device() has run, so it is unbound by\npci_remove_bus_device() instead of pci_stop_bus_device().  Because the\npci_bus has already been destroyed at that point, accesses to it result in\na use-after-free.\n\nOne might conclude that driver binding needs to be prevented after\npci_stop_bus_device() has run.  However it seems risky that pci_slot points\nto pci_bus without holding a reference.  Solely relying on correct ordering\nof driver unbind versus pci_bus destruction is certainly not defensive\nprogramming.\n\nIf pci_slot has a need to access data in pci_bus, it ought to acquire a\nreference.  Amend pci_create_slot() accordingly.  Dennis reports that the\ncrash is not reproducible with this change.\n\nAbridged stacktrace:\n\n  pcieport 0000:00:07.0: PME: Signaling with IRQ 156\n  pcieport 0000:00:07.0: pciehp: Slot #12 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ IbPresDis- LLActRep+\n  pci_bus 0000:20: dev 00, created physical slot 12\n  pcieport 0000:00:07.0: pciehp: Slot(12): Card not present\n  ...\n  pcieport 0000:21:02.0: pciehp: pcie_disable_notification: SLOTCTRL d8 write cmd 0\n  Oops: general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b6b6b: 0000 [#1] PREEMPT SMP NOPTI\n  CPU: 13 UID: 0 PID: 134 Comm: irq/156-pciehp Not tainted 6.11.0-devel+ #1\n  RIP: 0010:dev_driver_string+0x12/0x40\n  pci_destroy_slot\n  pciehp_remove\n  pcie_port_remove_service\n  device_release_driver_internal\n  bus_remove_device\n  device_del\n  device_unregister\n  remove_iter\n  device_for_each_child\n  pcie_portdrv_remove\n  pci_device_remove\n  device_release_driver_internal\n  bus_remove_device\n  device_del\n  pci_remove_bus_device (recursive invocation)\n  pci_remove_bus_device\n  pciehp_unconfigure_device\n  pciehp_disable_slot\n  pciehp_handle_presence_or_link_change\n  pciehp_ist(CVE-2024-53194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Don\u0026apos;t retire aborted MMIO instruction\n\nReturning an abort to the guest for an unsupported MMIO access is a\ndocumented feature of the KVM UAPI. Nevertheless, it\u0026apos;s clear that this\nplumbing has seen limited testing, since userspace can trivially cause a\nWARN in the MMIO return:\n\n  WARNING: CPU: 0 PID: 30558 at arch/arm64/include/asm/kvm_emulate.h:536 kvm_handle_mmio_return+0x46c/0x5c4 arch/arm64/include/asm/kvm_emulate.h:536\n  Call trace:\n   kvm_handle_mmio_return+0x46c/0x5c4 arch/arm64/include/asm/kvm_emulate.h:536\n   kvm_arch_vcpu_ioctl_run+0x98/0x15b4 arch/arm64/kvm/arm.c:1133\n   kvm_vcpu_ioctl+0x75c/0xa78 virt/kvm/kvm_main.c:4487\n   __do_sys_ioctl fs/ioctl.c:51 [inline]\n   __se_sys_ioctl fs/ioctl.c:893 [inline]\n   __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:893\n   __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]\n   invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49\n   el0_svc_common+0x1e0/0x23c arch/arm64/kernel/syscall.c:132\n   do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151\n   el0_svc+0x38/0x68 arch/arm64/kernel/entry-common.c:712\n   el0t_64_sync_handler+0x90/0xfc arch/arm64/kernel/entry-common.c:730\n   el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598\n\nThe splat is complaining that KVM is advancing PC while an exception is\npending, i.e. that KVM is retiring the MMIO instruction despite a\npending synchronous external abort. Womp womp.\n\nFix the glaring UAPI bug by skipping over all the MMIO emulation in\ncase there is a pending synchronous exception. Note that while userspace\nis capable of pending an asynchronous exception (SError, IRQ, or FIQ),\nit is still safe to retire the MMIO instruction in this case as (1) they\nare by definition asynchronous, and (2) KVM relies on hardware support\nfor pending/delivering these exceptions instead of the software state\nmachine for advancing PC.(CVE-2024-53196)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: fix potential array underflow in ucsi_ccg_sync_control()\n\nThe \u0026quot;command\u0026quot; variable can be controlled by the user via debugfs.  The\nworry is that if con_index is zero then \u0026quot;\u0026amp;uc-\u0026gt;ucsi-\u0026gt;connector[con_index\n- 1]\u0026quot; would be an array underflow.(CVE-2024-53203)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: lan78xx: Fix double free issue with interrupt buffer allocation\n\nIn lan78xx_probe(), the buffer `buf` was being freed twice: once\nimplicitly through `usb_free_urb(dev-\u0026gt;urb_intr)` with the\n`URB_FREE_BUFFER` flag and again explicitly by `kfree(buf)`. This caused\na double free issue.\n\nTo resolve this, reordered `kmalloc()` and `usb_alloc_urb()` calls to\nsimplify the initialization sequence and removed the redundant\n`kfree(buf)`.  Now, `buf` is allocated after `usb_alloc_urb()`, ensuring\nit is correctly managed by  `usb_fill_int_urb()` and freed by\n`usb_free_urb()` as intended.(CVE-2024-53213)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsvcrdma: fix miss destroy percpu_counter in svc_rdma_proc_init()\n\nThere\u0026apos;s issue as follows:\nRPC: Registered rdma transport module.\nRPC: Registered rdma backchannel transport module.\nRPC: Unregistered rdma transport module.\nRPC: Unregistered rdma backchannel transport module.\nBUG: unable to handle page fault for address: fffffbfff80c609a\nPGD 123fee067 P4D 123fee067 PUD 123fea067 PMD 10c624067 PTE 0\nOops: Oops: 0000 [#1] PREEMPT SMP KASAN NOPTI\nRIP: 0010:percpu_counter_destroy_many+0xf7/0x2a0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __die+0x1f/0x70\n page_fault_oops+0x2cd/0x860\n spurious_kernel_fault+0x36/0x450\n do_kern_addr_fault+0xca/0x100\n exc_page_fault+0x128/0x150\n asm_exc_page_fault+0x26/0x30\n percpu_counter_destroy_many+0xf7/0x2a0\n mmdrop+0x209/0x350\n finish_task_switch.isra.0+0x481/0x840\n schedule_tail+0xe/0xd0\n ret_from_fork+0x23/0x80\n ret_from_fork_asm+0x1a/0x30\n \u0026lt;/TASK\u0026gt;\n\nIf register_sysctl() return NULL, then svc_rdma_proc_cleanup() will not\ndestroy the percpu counters which init in svc_rdma_proc_init().\nIf CONFIG_HOTPLUG_CPU is enabled, residual nodes may be in the\n\u0026apos;percpu_counters\u0026apos; list. The above issue may occur once the module is\nremoved. If the CONFIG_HOTPLUG_CPU configuration is not enabled, memory\nleakage occurs.\nTo solve above issue just destroy all percpu counters when\nregister_sysctl() return NULL.(CVE-2024-53215)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix race in concurrent f2fs_stop_gc_thread\n\nIn my test case, concurrent calls to f2fs shutdown report the following\nstack trace:\n\n Oops: general protection fault, probably for non-canonical address 0xc6cfff63bb5513fc: 0000 [#1] PREEMPT SMP PTI\n CPU: 0 UID: 0 PID: 678 Comm: f2fs_rep_shutdo Not tainted 6.12.0-rc5-next-20241029-g6fb2fa9805c5-dirty #85\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  ? show_regs+0x8b/0xa0\n  ? __die_body+0x26/0xa0\n  ? die_addr+0x54/0x90\n  ? exc_general_protection+0x24b/0x5c0\n  ? asm_exc_general_protection+0x26/0x30\n  ? kthread_stop+0x46/0x390\n  f2fs_stop_gc_thread+0x6c/0x110\n  f2fs_do_shutdown+0x309/0x3a0\n  f2fs_ioc_shutdown+0x150/0x1c0\n  __f2fs_ioctl+0xffd/0x2ac0\n  f2fs_ioctl+0x76/0xe0\n  vfs_ioctl+0x23/0x60\n  __x64_sys_ioctl+0xce/0xf0\n  x64_sys_call+0x2b1b/0x4540\n  do_syscall_64+0xa7/0x240\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe root cause is a race condition in f2fs_stop_gc_thread() called from\ndifferent f2fs shutdown paths:\n\n  [CPU0]                       [CPU1]\n  ----------------------       -----------------------\n  f2fs_stop_gc_thread          f2fs_stop_gc_thread\n                                 gc_th = sbi-\u0026gt;gc_thread\n    gc_th = sbi-\u0026gt;gc_thread\n    kfree(gc_th)\n    sbi-\u0026gt;gc_thread = NULL\n                                 \u0026lt; gc_th != NULL \u0026gt;\n                                 kthread_stop(gc_th-\u0026gt;f2fs_gc_task) //UAF\n\nThe commit c7f114d864ac (\u0026quot;f2fs: fix to avoid use-after-free in\nf2fs_stop_gc_thread()\u0026quot;) attempted to fix this issue by using a read\nsemaphore to prevent races between shutdown and remount threads, but\nit fails to prevent all race conditions.\n\nFix it by converting to write lock of s_umount in f2fs_do_shutdown().(CVE-2024-53218)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvirtiofs: use pages instead of pointer for kernel direct IO\n\nWhen trying to insert a 10MB kernel module kept in a virtio-fs with cache\ndisabled, the following warning was reported:\n\n  ------------[ cut here ]------------\n  WARNING: CPU: 1 PID: 404 at mm/page_alloc.c:4551 ......\n  Modules linked in:\n  CPU: 1 PID: 404 Comm: insmod Not tainted 6.9.0-rc5+ #123\n  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) ......\n  RIP: 0010:__alloc_pages+0x2bf/0x380\n  ......\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   ? __warn+0x8e/0x150\n   ? __alloc_pages+0x2bf/0x380\n   __kmalloc_large_node+0x86/0x160\n   __kmalloc+0x33c/0x480\n   virtio_fs_enqueue_req+0x240/0x6d0\n   virtio_fs_wake_pending_and_unlock+0x7f/0x190\n   queue_request_and_unlock+0x55/0x60\n   fuse_simple_request+0x152/0x2b0\n   fuse_direct_io+0x5d2/0x8c0\n   fuse_file_read_iter+0x121/0x160\n   __kernel_read+0x151/0x2d0\n   kernel_read+0x45/0x50\n   kernel_read_file+0x1a9/0x2a0\n   init_module_from_file+0x6a/0xe0\n   idempotent_init_module+0x175/0x230\n   __x64_sys_finit_module+0x5d/0xb0\n   x64_sys_call+0x1c3/0x9e0\n   do_syscall_64+0x3d/0xc0\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   ......\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThe warning is triggered as follows:\n\n1) syscall finit_module() handles the module insertion and it invokes\nkernel_read_file() to read the content of the module first.\n\n2) kernel_read_file() allocates a 10MB buffer by using vmalloc() and\npasses it to kernel_read(). kernel_read() constructs a kvec iter by\nusing iov_iter_kvec() and passes it to fuse_file_read_iter().\n\n3) virtio-fs disables the cache, so fuse_file_read_iter() invokes\nfuse_direct_io(). As for now, the maximal read size for kvec iter is\nonly limited by fc-\u0026gt;max_read. For virtio-fs, max_read is UINT_MAX, so\nfuse_direct_io() doesn\u0026apos;t split the 10MB buffer. It saves the address and\nthe size of the 10MB-sized buffer in out_args[0] of a fuse request and\npasses the fuse request to virtio_fs_wake_pending_and_unlock().\n\n4) virtio_fs_wake_pending_and_unlock() uses virtio_fs_enqueue_req() to\nqueue the request. Because virtiofs need DMA-able address, so\nvirtio_fs_enqueue_req() uses kmalloc() to allocate a bounce buffer for\nall fuse args, copies these args into the bounce buffer and passed the\nphysical address of the bounce buffer to virtiofsd. The total length of\nthese fuse args for the passed fuse request is about 10MB, so\ncopy_args_to_argbuf() invokes kmalloc() with a 10MB size parameter and\nit triggers the warning in __alloc_pages():\n\n\tif (WARN_ON_ONCE_GFP(order \u0026gt; MAX_PAGE_ORDER, gfp))\n\t\treturn NULL;\n\n5) virtio_fs_enqueue_req() will retry the memory allocation in a\nkworker, but it won\u0026apos;t help, because kmalloc() will always return NULL\ndue to the abnormal size and finit_module() will hang forever.\n\nA feasible solution is to limit the value of max_read for virtio-fs, so\nthe length passed to kmalloc() will be limited. However it will affect\nthe maximal read size for normal read. And for virtio-fs write initiated\nfrom kernel, it has the similar problem but now there is no way to limit\nfc-\u0026gt;max_write in kernel.\n\nSo instead of limiting both the values of max_read and max_write in\nkernel, introducing use_pages_for_kvec_io in fuse_conn and setting it as\ntrue in virtiofs. When use_pages_for_kvec_io is enabled, fuse will use\npages instead of pointer to pass the KVEC_IO data.\n\nAfter switching to pages for KVEC_IO data, these pages will be used for\nDMA through virtio-fs. If these pages are backed by vmalloc(),\n{flush|invalidate}_kernel_vmap_range() are necessary to flush or\ninvalidate the cache before the DMA operation. So add two new fields in\nfuse_args_pages to record the base address of vmalloc area and the\ncondition indicating whether invalidation is needed. Perform the flush\nin fuse_get_user_pages() for write operations and the invalidation in\nfuse_release_user_pages() for read operations.\n\nIt may seem necessary to introduce another fie\n---truncated---(CVE-2024-53219)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/mlx5: Move events notifier registration to be after device registration\n\nMove pkey change work initialization and cleanup from device resources\nstage to notifier stage, since this is the stage which handles this work\nevents.\n\nFix a race between the device deregistration and pkey change work by moving\nMLX5_IB_STAGE_DEVICE_NOTIFIER to be after MLX5_IB_STAGE_IB_REG in order to\nensure that the notifier is deregistered before the device during cleanup.\nWhich ensures there are no works that are being executed after the\ndevice has already unregistered which can cause the panic below.\n\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nPGD 0 P4D 0\nOops: 0000 [#1] PREEMPT SMP PTI\nCPU: 1 PID: 630071 Comm: kworker/1:2 Kdump: loaded Tainted: G W OE --------- --- 5.14.0-162.6.1.el9_1.x86_64 #1\nHardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 02/27/2023\nWorkqueue: events pkey_change_handler [mlx5_ib]\nRIP: 0010:setup_qp+0x38/0x1f0 [mlx5_ib]\nCode: ee 41 54 45 31 e4 55 89 f5 53 48 89 fb 48 83 ec 20 8b 77 08 65 48 8b 04 25 28 00 00 00 48 89 44 24 18 48 8b 07 48 8d 4c 24 16 \u0026lt;4c\u0026gt; 8b 38 49 8b 87 80 0b 00 00 4c 89 ff 48 8b 80 08 05 00 00 8b 40\nRSP: 0018:ffffbcc54068be20 EFLAGS: 00010282\nRAX: 0000000000000000 RBX: ffff954054494128 RCX: ffffbcc54068be36\nRDX: ffff954004934000 RSI: 0000000000000001 RDI: ffff954054494128\nRBP: 0000000000000023 R08: ffff954001be2c20 R09: 0000000000000001\nR10: ffff954001be2c20 R11: ffff9540260133c0 R12: 0000000000000000\nR13: 0000000000000023 R14: 0000000000000000 R15: ffff9540ffcb0905\nFS: 0000000000000000(0000) GS:ffff9540ffc80000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000000 CR3: 000000010625c001 CR4: 00000000003706e0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\nmlx5_ib_gsi_pkey_change+0x20/0x40 [mlx5_ib]\nprocess_one_work+0x1e8/0x3c0\nworker_thread+0x50/0x3b0\n? rescuer_thread+0x380/0x380\nkthread+0x149/0x170\n? set_kthread_struct+0x50/0x50\nret_from_fork+0x22/0x30\nModules linked in: rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_umad(OE) mlx5_ib(OE) mlx5_fwctl(OE) fwctl(OE) ib_uverbs(OE) mlx5_core(OE) mlxdevm(OE) ib_core(OE) mlx_compat(OE) psample mlxfw(OE) tls knem(OE) netconsole nfsv3 nfs_acl nfs lockd grace fscache netfs qrtr rfkill sunrpc intel_rapl_msr intel_rapl_common rapl hv_balloon hv_utils i2c_piix4 pcspkr joydev fuse ext4 mbcache jbd2 sr_mod sd_mod cdrom t10_pi sg ata_generic pci_hyperv pci_hyperv_intf hyperv_drm drm_shmem_helper drm_kms_helper hv_storvsc syscopyarea hv_netvsc sysfillrect sysimgblt hid_hyperv fb_sys_fops scsi_transport_fc hyperv_keyboard drm ata_piix crct10dif_pclmul crc32_pclmul crc32c_intel libata ghash_clmulni_intel hv_vmbus serio_raw [last unloaded: ib_core]\nCR2: 0000000000000000\n---[ end trace f6f8be4eae12f7bc ]---(CVE-2024-53224)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rxe: Fix the qp flush warnings in req\n\nWhen the qp is in error state, the status of WQEs in the queue should be\nset to error. Or else the following will appear.\n\n[  920.617269] WARNING: CPU: 1 PID: 21 at drivers/infiniband/sw/rxe/rxe_comp.c:756 rxe_completer+0x989/0xcc0 [rdma_rxe]\n[  920.617744] Modules linked in: rnbd_client(O) rtrs_client(O) rtrs_core(O) rdma_ucm rdma_cm iw_cm ib_cm crc32_generic rdma_rxe ip6_udp_tunnel udp_tunnel ib_uverbs ib_core loop brd null_blk ipv6\n[  920.618516] CPU: 1 PID: 21 Comm: ksoftirqd/1 Tainted: G           O       6.1.113-storage+ #65\n[  920.618986] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014\n[  920.619396] RIP: 0010:rxe_completer+0x989/0xcc0 [rdma_rxe]\n[  920.619658] Code: 0f b6 84 24 3a 02 00 00 41 89 84 24 44 04 00 00 e9 2a f7 ff ff 39 ca bb 03 00 00 00 b8 0e 00 00 00 48 0f 45 d8 e9 15 f7 ff ff \u0026lt;0f\u0026gt; 0b e9 cb f8 ff ff 41 bf f5 ff ff ff e9 08 f8 ff ff 49 8d bc 24\n[  920.620482] RSP: 0018:ffff97b7c00bbc38 EFLAGS: 00010246\n[  920.620817] RAX: 0000000000000000 RBX: 000000000000000c RCX: 0000000000000008\n[  920.621183] RDX: ffff960dc396ebc0 RSI: 0000000000005400 RDI: ffff960dc4e2fbac\n[  920.621548] RBP: 0000000000000000 R08: 0000000000000001 R09: ffffffffac406450\n[  920.621884] R10: ffffffffac4060c0 R11: 0000000000000001 R12: ffff960dc4e2f800\n[  920.622254] R13: ffff960dc4e2f928 R14: ffff97b7c029c580 R15: 0000000000000000\n[  920.622609] FS:  0000000000000000(0000) GS:ffff960ef7d00000(0000) knlGS:0000000000000000\n[  920.622979] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  920.623245] CR2: 00007fa056965e90 CR3: 00000001107f1000 CR4: 00000000000006e0\n[  920.623680] Call Trace:\n[  920.623815]  \u0026lt;TASK\u0026gt;\n[  920.623933]  ? __warn+0x79/0xc0\n[  920.624116]  ? rxe_completer+0x989/0xcc0 [rdma_rxe]\n[  920.624356]  ? report_bug+0xfb/0x150\n[  920.624594]  ? handle_bug+0x3c/0x60\n[  920.624796]  ? exc_invalid_op+0x14/0x70\n[  920.624976]  ? asm_exc_invalid_op+0x16/0x20\n[  920.625203]  ? rxe_completer+0x989/0xcc0 [rdma_rxe]\n[  920.625474]  ? rxe_completer+0x329/0xcc0 [rdma_rxe]\n[  920.625749]  rxe_do_task+0x80/0x110 [rdma_rxe]\n[  920.626037]  rxe_requester+0x625/0xde0 [rdma_rxe]\n[  920.626310]  ? rxe_cq_post+0xe2/0x180 [rdma_rxe]\n[  920.626583]  ? do_complete+0x18d/0x220 [rdma_rxe]\n[  920.626812]  ? rxe_completer+0x1a3/0xcc0 [rdma_rxe]\n[  920.627050]  rxe_do_task+0x80/0x110 [rdma_rxe]\n[  920.627285]  tasklet_action_common.constprop.0+0xa4/0x120\n[  920.627522]  handle_softirqs+0xc2/0x250\n[  920.627728]  ? sort_range+0x20/0x20\n[  920.627942]  run_ksoftirqd+0x1f/0x30\n[  920.628158]  smpboot_thread_fn+0xc7/0x1b0\n[  920.628334]  kthread+0xd6/0x100\n[  920.628504]  ? kthread_complete_and_exit+0x20/0x20\n[  920.628709]  ret_from_fork+0x1f/0x30\n[  920.628892]  \u0026lt;/TASK\u0026gt;(CVE-2024-53229)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: CPPC: Fix possible null-ptr-deref for cpufreq_cpu_get_raw()\n\ncpufreq_cpu_get_raw() may return NULL if the cpu is not in\npolicy-\u0026gt;cpus cpu mask and it will cause null pointer dereference.(CVE-2024-53231)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nerofs: handle NONHEAD !delta[1] lclusters gracefully\n\nsyzbot reported a WARNING in iomap_iter_done:\n iomap_fiemap+0x73b/0x9b0 fs/iomap/fiemap.c:80\n ioctl_fiemap fs/ioctl.c:220 [inline]\n\nGenerally, NONHEAD lclusters won\u0026apos;t have delta[1]==0, except for crafted\nimages and filesystems created by pre-1.0 mkfs versions.\n\nPreviously, it would immediately bail out if delta[1]==0, which led to\ninadequate decompressed lengths (thus FIEMAP is impacted).  Treat it as\ndelta[1]=1 to work around these legacy mkfs versions.\n\n`lclusterbits \u0026gt; 14` is illegal for compact indexes, error out too.(CVE-2024-53234)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nALSA: 6fire: Release resources at card release\n\nThe current 6fire code tries to release the resources right after the\ncall of usb6fire_chip_abort().  But at this moment, the card object\nmight be still in use (as we\u0026apos;re calling snd_card_free_when_closed()).\n\nFor avoid potential UAFs, move the release of resources to the card\u0026apos;s\nprivate_free instead of the manual call of usb6fire_chip_destroy() at\nthe USB disconnect callback.(CVE-2024-53239)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/xen: don\u0026apos;t do PV iret hypercall through hypercall page\n\nInstead of jumping to the Xen hypercall page for doing the iret\nhypercall, directly code the required sequence in xen-asm.S.\n\nThis is done in preparation of no longer using hypercall page at all,\nas it has shown to cause problems with speculation mitigations.\n\nThis is part of XSA-466 / CVE-2024-53241.(CVE-2024-53241)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: renesas: rswitch: avoid use-after-put for a device tree node\n\nThe device tree node saved in the rswitch_device structure is used at\nseveral driver locations. So passing this node to of_node_put() after\nthe first use is wrong.\n\nMove of_node_put() for this node to exit paths.(CVE-2024-55639)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath12k: Skip Rx TID cleanup for self peer\n\nDuring peer create, dp setup for the peer is done where Rx TID is\nupdated for all the TIDs. Peer object for self peer will not go through\ndp setup.\n\nWhen core halts, dp cleanup is done for all the peers. While cleanup,\nrx_tid::ab is accessed which causes below stack trace for self peer.\n\nWARNING: CPU: 6 PID: 12297 at drivers/net/wireless/ath/ath12k/dp_rx.c:851\nCall Trace:\n__warn+0x7b/0x1a0\nath12k_dp_rx_frags_cleanup+0xd2/0xe0 [ath12k]\nreport_bug+0x10b/0x200\nhandle_bug+0x3f/0x70\nexc_invalid_op+0x13/0x60\nasm_exc_invalid_op+0x16/0x20\nath12k_dp_rx_frags_cleanup+0xd2/0xe0 [ath12k]\nath12k_dp_rx_frags_cleanup+0xca/0xe0 [ath12k]\nath12k_dp_rx_peer_tid_cleanup+0x39/0xa0 [ath12k]\nath12k_mac_peer_cleanup_all+0x61/0x100 [ath12k]\nath12k_core_halt+0x3b/0x100 [ath12k]\nath12k_core_reset+0x494/0x4c0 [ath12k]\n\nsta object in peer will be updated when remote peer is created. Hence\nuse peer::sta to detect the self peer and skip the cleanup.\n\nTested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1\nTested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3(CVE-2024-56543)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrivers: soc: xilinx: add the missing kfree in xlnx_add_cb_for_suspend()\n\nIf we fail to allocate memory for cb_data by kmalloc, the memory\nallocation for eve_data is never freed, add the missing kfree()\nin the error handling path.(CVE-2024-56546)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncachefiles: Fix NULL pointer dereference in object-\u0026gt;file\n\nAt present, the object-\u0026gt;file has the NULL pointer dereference problem in\nondemand-mode. The root cause is that the allocated fd and object-\u0026gt;file\nlifetime are inconsistent, and the user-space invocation to anon_fd uses\nobject-\u0026gt;file. Following is the process that triggers the issue:\n\n\t  [write fd]\t\t\t\t[umount]\ncachefiles_ondemand_fd_write_iter\n\t\t\t\t       fscache_cookie_state_machine\n\t\t\t\t\t cachefiles_withdraw_cookie\n  if (!file) return -ENOBUFS\n\t\t\t\t\t   cachefiles_clean_up_object\n\t\t\t\t\t     cachefiles_unmark_inode_in_use\n\t\t\t\t\t     fput(object-\u0026gt;file)\n\t\t\t\t\t     object-\u0026gt;file = NULL\n  // file NULL pointer dereference!\n  __cachefiles_write(..., file, ...)\n\nFix this issue by add an additional reference count to the object-\u0026gt;file\nbefore write/llseek, and decrement after it finished.(CVE-2024-56549)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ni3c: master: Fix miss free init_dyn_addr at i3c_master_put_i3c_addrs()\n\nif (dev-\u0026gt;boardinfo \u0026amp;\u0026amp; dev-\u0026gt;boardinfo-\u0026gt;init_dyn_addr)\n                                      ^^^ here check \u0026quot;init_dyn_addr\u0026quot;\n\ti3c_bus_set_addr_slot_status(\u0026amp;master-\u0026gt;bus, dev-\u0026gt;info.dyn_addr, ...)\n\t\t\t\t\t\t             ^^^^\n\t\t\t\t\t\t\tfree \u0026quot;dyn_addr\u0026quot;\nFix copy/paste error \u0026quot;dyn_addr\u0026quot; by replacing it with \u0026quot;init_dyn_addr\u0026quot;.(CVE-2024-56562)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\novl: Filter invalid inodes with missing lookup function\n\nAdd a check to the ovl_dentry_weird() function to prevent the\nprocessing of directory inodes that lack the lookup function.\nThis is important because such inodes can cause errors in overlayfs\nwhen passed to the lowerstack.(CVE-2024-56570)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: platform: allegro-dvt: Fix possible memory leak in allocate_buffers_internal()\n\nThe buffer in the loop should be released under the exception path,\notherwise there may be a memory leak here.\n\nTo mitigate this, free the buffer when allegro_alloc_buffer fails.(CVE-2024-56572)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix use-after-free in btrfs_encoded_read_endio()\n\nShinichiro reported the following use-after free that sometimes is\nhappening in our CI system when running fstests\u0026apos; btrfs/284 on a TCMU\nrunner device:\n\n  BUG: KASAN: slab-use-after-free in lock_release+0x708/0x780\n  Read of size 8 at addr ffff888106a83f18 by task kworker/u80:6/219\n\n  CPU: 8 UID: 0 PID: 219 Comm: kworker/u80:6 Not tainted 6.12.0-rc6-kts+ #15\n  Hardware name: Supermicro Super Server/X11SPi-TF, BIOS 3.3 02/21/2020\n  Workqueue: btrfs-endio btrfs_end_bio_work [btrfs]\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x6e/0xa0\n   ? lock_release+0x708/0x780\n   print_report+0x174/0x505\n   ? lock_release+0x708/0x780\n   ? __virt_addr_valid+0x224/0x410\n   ? lock_release+0x708/0x780\n   kasan_report+0xda/0x1b0\n   ? lock_release+0x708/0x780\n   ? __wake_up+0x44/0x60\n   lock_release+0x708/0x780\n   ? __pfx_lock_release+0x10/0x10\n   ? __pfx_do_raw_spin_lock+0x10/0x10\n   ? lock_is_held_type+0x9a/0x110\n   _raw_spin_unlock_irqrestore+0x1f/0x60\n   __wake_up+0x44/0x60\n   btrfs_encoded_read_endio+0x14b/0x190 [btrfs]\n   btrfs_check_read_bio+0x8d9/0x1360 [btrfs]\n   ? lock_release+0x1b0/0x780\n   ? trace_lock_acquire+0x12f/0x1a0\n   ? __pfx_btrfs_check_read_bio+0x10/0x10 [btrfs]\n   ? process_one_work+0x7e3/0x1460\n   ? lock_acquire+0x31/0xc0\n   ? process_one_work+0x7e3/0x1460\n   process_one_work+0x85c/0x1460\n   ? __pfx_process_one_work+0x10/0x10\n   ? assign_work+0x16c/0x240\n   worker_thread+0x5e6/0xfc0\n   ? __pfx_worker_thread+0x10/0x10\n   kthread+0x2c3/0x3a0\n   ? __pfx_kthread+0x10/0x10\n   ret_from_fork+0x31/0x70\n   ? __pfx_kthread+0x10/0x10\n   ret_from_fork_asm+0x1a/0x30\n   \u0026lt;/TASK\u0026gt;\n\n  Allocated by task 3661:\n   kasan_save_stack+0x30/0x50\n   kasan_save_track+0x14/0x30\n   __kasan_kmalloc+0xaa/0xb0\n   btrfs_encoded_read_regular_fill_pages+0x16c/0x6d0 [btrfs]\n   send_extent_data+0xf0f/0x24a0 [btrfs]\n   process_extent+0x48a/0x1830 [btrfs]\n   changed_cb+0x178b/0x2ea0 [btrfs]\n   btrfs_ioctl_send+0x3bf9/0x5c20 [btrfs]\n   _btrfs_ioctl_send+0x117/0x330 [btrfs]\n   btrfs_ioctl+0x184a/0x60a0 [btrfs]\n   __x64_sys_ioctl+0x12e/0x1a0\n   do_syscall_64+0x95/0x180\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n  Freed by task 3661:\n   kasan_save_stack+0x30/0x50\n   kasan_save_track+0x14/0x30\n   kasan_save_free_info+0x3b/0x70\n   __kasan_slab_free+0x4f/0x70\n   kfree+0x143/0x490\n   btrfs_encoded_read_regular_fill_pages+0x531/0x6d0 [btrfs]\n   send_extent_data+0xf0f/0x24a0 [btrfs]\n   process_extent+0x48a/0x1830 [btrfs]\n   changed_cb+0x178b/0x2ea0 [btrfs]\n   btrfs_ioctl_send+0x3bf9/0x5c20 [btrfs]\n   _btrfs_ioctl_send+0x117/0x330 [btrfs]\n   btrfs_ioctl+0x184a/0x60a0 [btrfs]\n   __x64_sys_ioctl+0x12e/0x1a0\n   do_syscall_64+0x95/0x180\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n  The buggy address belongs to the object at ffff888106a83f00\n   which belongs to the cache kmalloc-rnd-07-96 of size 96\n  The buggy address is located 24 bytes inside of\n   freed 96-byte region [ffff888106a83f00, ffff888106a83f60)\n\n  The buggy address belongs to the physical page:\n  page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888106a83800 pfn:0x106a83\n  flags: 0x17ffffc0000000(node=0|zone=2|lastcpupid=0x1fffff)\n  page_type: f5(slab)\n  raw: 0017ffffc0000000 ffff888100053680 ffffea0004917200 0000000000000004\n  raw: ffff888106a83800 0000000080200019 00000001f5000000 0000000000000000\n  page dumped because: kasan: bad access detected\n\n  Memory state around the buggy address:\n   ffff888106a83e00: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc\n   ffff888106a83e80: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc\n  \u0026gt;ffff888106a83f00: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc\n                              ^\n   ffff888106a83f80: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc\n   ffff888106a84000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n  ==================================================================\n\nFurther analyzing the trace and \n---truncated---(CVE-2024-56582)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: Fix warning in migrate_enable for boosted tasks\n\nWhen running the following command:\n\nwhile true; do\n    stress-ng --cyclic 30 --timeout 30s --minimize --quiet\ndone\n\na warning is eventually triggered:\n\nWARNING: CPU: 43 PID: 2848 at kernel/sched/deadline.c:794\nsetup_new_dl_entity+0x13e/0x180\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? show_trace_log_lvl+0x1c4/0x2df\n ? enqueue_dl_entity+0x631/0x6e0\n ? setup_new_dl_entity+0x13e/0x180\n ? __warn+0x7e/0xd0\n ? report_bug+0x11a/0x1a0\n ? handle_bug+0x3c/0x70\n ? exc_invalid_op+0x14/0x70\n ? asm_exc_invalid_op+0x16/0x20\n enqueue_dl_entity+0x631/0x6e0\n enqueue_task_dl+0x7d/0x120\n __do_set_cpus_allowed+0xe3/0x280\n __set_cpus_allowed_ptr_locked+0x140/0x1d0\n __set_cpus_allowed_ptr+0x54/0xa0\n migrate_enable+0x7e/0x150\n rt_spin_unlock+0x1c/0x90\n group_send_sig_info+0xf7/0x1a0\n ? kill_pid_info+0x1f/0x1d0\n kill_pid_info+0x78/0x1d0\n kill_proc_info+0x5b/0x110\n __x64_sys_kill+0x93/0xc0\n do_syscall_64+0x5c/0xf0\n entry_SYSCALL_64_after_hwframe+0x6e/0x76\n RIP: 0033:0x7f0dab31f92b\n\nThis warning occurs because set_cpus_allowed dequeues and enqueues tasks\nwith the ENQUEUE_RESTORE flag set. If the task is boosted, the warning\nis triggered. A boosted task already had its parameters set by\nrt_mutex_setprio, and a new call to setup_new_dl_entity is unnecessary,\nhence the WARN_ON call.\n\nCheck if we are requeueing a boosted task and avoid calling\nsetup_new_dl_entity if that\u0026apos;s the case.(CVE-2024-56583)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: Fix sleeping in atomic context for PREEMPT_RT\n\nCommit bab1c299f3945ffe79 (\u0026quot;LoongArch: Fix sleeping in atomic context in\nsetup_tlb_handler()\u0026quot;) changes the gfp flag from GFP_KERNEL to GFP_ATOMIC\nfor alloc_pages_node(). However, for PREEMPT_RT kernels we can still get\na \u0026quot;sleeping in atomic context\u0026quot; error:\n\n[    0.372259] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48\n[    0.372266] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1\n[    0.372268] preempt_count: 1, expected: 0\n[    0.372270] RCU nest depth: 1, expected: 1\n[    0.372272] 3 locks held by swapper/1/0:\n[    0.372274]  #0: 900000000c9f5e60 (\u0026amp;pcp-\u0026gt;lock){+.+.}-{3:3}, at: get_page_from_freelist+0x524/0x1c60\n[    0.372294]  #1: 90000000087013b8 (rcu_read_lock){....}-{1:3}, at: rt_spin_trylock+0x50/0x140\n[    0.372305]  #2: 900000047fffd388 (\u0026amp;zone-\u0026gt;lock){+.+.}-{3:3}, at: __rmqueue_pcplist+0x30c/0xea0\n[    0.372314] irq event stamp: 0\n[    0.372316] hardirqs last  enabled at (0): [\u0026lt;0000000000000000\u0026gt;] 0x0\n[    0.372322] hardirqs last disabled at (0): [\u0026lt;9000000005947320\u0026gt;] copy_process+0x9c0/0x26e0\n[    0.372329] softirqs last  enabled at (0): [\u0026lt;9000000005947320\u0026gt;] copy_process+0x9c0/0x26e0\n[    0.372335] softirqs last disabled at (0): [\u0026lt;0000000000000000\u0026gt;] 0x0\n[    0.372341] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.12.0-rc7+ #1891\n[    0.372346] Hardware name: Loongson Loongson-3A5000-7A1000-1w-CRB/Loongson-LS3A5000-7A1000-1w-CRB, BIOS vUDK2018-LoongArch-V2.0.0-prebeta9 10/21/2022\n[    0.372349] Stack : 0000000000000089 9000000005a0db9c 90000000071519c8 9000000100388000\n[    0.372486]         900000010038b890 0000000000000000 900000010038b898 9000000007e53788\n[    0.372492]         900000000815bcc8 900000000815bcc0 900000010038b700 0000000000000001\n[    0.372498]         0000000000000001 4b031894b9d6b725 00000000055ec000 9000000100338fc0\n[    0.372503]         00000000000000c4 0000000000000001 000000000000002d 0000000000000003\n[    0.372509]         0000000000000030 0000000000000003 00000000055ec000 0000000000000003\n[    0.372515]         900000000806d000 9000000007e53788 00000000000000b0 0000000000000004\n[    0.372521]         0000000000000000 0000000000000000 900000000c9f5f10 0000000000000000\n[    0.372526]         90000000076f12d8 9000000007e53788 9000000005924778 0000000000000000\n[    0.372532]         00000000000000b0 0000000000000004 0000000000000000 0000000000070000\n[    0.372537]         ...\n[    0.372540] Call Trace:\n[    0.372542] [\u0026lt;9000000005924778\u0026gt;] show_stack+0x38/0x180\n[    0.372548] [\u0026lt;90000000071519c4\u0026gt;] dump_stack_lvl+0x94/0xe4\n[    0.372555] [\u0026lt;900000000599b880\u0026gt;] __might_resched+0x1a0/0x260\n[    0.372561] [\u0026lt;90000000071675cc\u0026gt;] rt_spin_lock+0x4c/0x140\n[    0.372565] [\u0026lt;9000000005cbb768\u0026gt;] __rmqueue_pcplist+0x308/0xea0\n[    0.372570] [\u0026lt;9000000005cbed84\u0026gt;] get_page_from_freelist+0x564/0x1c60\n[    0.372575] [\u0026lt;9000000005cc0d98\u0026gt;] __alloc_pages_noprof+0x218/0x1820\n[    0.372580] [\u0026lt;900000000593b36c\u0026gt;] tlb_init+0x1ac/0x298\n[    0.372585] [\u0026lt;9000000005924b74\u0026gt;] per_cpu_trap_init+0x114/0x140\n[    0.372589] [\u0026lt;9000000005921964\u0026gt;] cpu_probe+0x4e4/0xa60\n[    0.372592] [\u0026lt;9000000005934874\u0026gt;] start_secondary+0x34/0xc0\n[    0.372599] [\u0026lt;900000000715615c\u0026gt;] smpboot_entry+0x64/0x6c\n\nThis is because in PREEMPT_RT kernels normal spinlocks are replaced by\nrt spinlocks and rt_spin_lock() will cause sleeping. Fix it by disabling\nNUMA optimization completely for PREEMPT_RT kernels.(CVE-2024-56585)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix f2fs_bug_on when uninstalling filesystem call f2fs_evict_inode.\n\ncreating a large files during checkpoint disable until it runs out of\nspace and then delete it, then remount to enable checkpoint again, and\nthen unmount the filesystem triggers the f2fs_bug_on as below:\n\n------------[ cut here ]------------\nkernel BUG at fs/f2fs/inode.c:896!\nCPU: 2 UID: 0 PID: 1286 Comm: umount Not tainted 6.11.0-rc7-dirty #360\nOops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI\nRIP: 0010:f2fs_evict_inode+0x58c/0x610\nCall Trace:\n __die_body+0x15/0x60\n die+0x33/0x50\n do_trap+0x10a/0x120\n f2fs_evict_inode+0x58c/0x610\n do_error_trap+0x60/0x80\n f2fs_evict_inode+0x58c/0x610\n exc_invalid_op+0x53/0x60\n f2fs_evict_inode+0x58c/0x610\n asm_exc_invalid_op+0x16/0x20\n f2fs_evict_inode+0x58c/0x610\n evict+0x101/0x260\n dispose_list+0x30/0x50\n evict_inodes+0x140/0x190\n generic_shutdown_super+0x2f/0x150\n kill_block_super+0x11/0x40\n kill_f2fs_super+0x7d/0x140\n deactivate_locked_super+0x2a/0x70\n cleanup_mnt+0xb3/0x140\n task_work_run+0x61/0x90\n\nThe root cause is: creating large files during disable checkpoint\nperiod results in not enough free segments, so when writing back root\ninode will failed in f2fs_enable_checkpoint. When umount the file\nsystem after enabling checkpoint, the root inode is dirty in\nf2fs_evict_inode function, which triggers BUG_ON. The steps to\nreproduce are as follows:\n\ndd if=/dev/zero of=f2fs.img bs=1M count=55\nmount f2fs.img f2fs_dir -o checkpoint=disable:10%\ndd if=/dev/zero of=big bs=1M count=50\nsync\nrm big\nmount -o remount,checkpoint=enable f2fs_dir\numount f2fs_dir\n\nLet\u0026apos;s redirty inode when there is not free segments during checkpoint\nis disable.(CVE-2024-56586)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Call free_htab_elem() after htab_unlock_bucket()\n\nFor htab of maps, when the map is removed from the htab, it may hold the\nlast reference of the map. bpf_map_fd_put_ptr() will invoke\nbpf_map_free_id() to free the id of the removed map element. However,\nbpf_map_fd_put_ptr() is invoked while holding a bucket lock\n(raw_spin_lock_t), and bpf_map_free_id() attempts to acquire map_idr_lock\n(spinlock_t), triggering the following lockdep warning:\n\n  =============================\n  [ BUG: Invalid wait context ]\n  6.11.0-rc4+ #49 Not tainted\n  -----------------------------\n  test_maps/4881 is trying to lock:\n  ffffffff84884578 (map_idr_lock){+...}-{3:3}, at: bpf_map_free_id.part.0+0x21/0x70\n  other info that might help us debug this:\n  context-{5:5}\n  2 locks held by test_maps/4881:\n   #0: ffffffff846caf60 (rcu_read_lock){....}-{1:3}, at: bpf_fd_htab_map_update_elem+0xf9/0x270\n   #1: ffff888149ced148 (\u0026amp;htab-\u0026gt;lockdep_key#2){....}-{2:2}, at: htab_map_update_elem+0x178/0xa80\n  stack backtrace:\n  CPU: 0 UID: 0 PID: 4881 Comm: test_maps Not tainted 6.11.0-rc4+ #49\n  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), ...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x6e/0xb0\n   dump_stack+0x10/0x20\n   __lock_acquire+0x73e/0x36c0\n   lock_acquire+0x182/0x450\n   _raw_spin_lock_irqsave+0x43/0x70\n   bpf_map_free_id.part.0+0x21/0x70\n   bpf_map_put+0xcf/0x110\n   bpf_map_fd_put_ptr+0x9a/0xb0\n   free_htab_elem+0x69/0xe0\n   htab_map_update_elem+0x50f/0xa80\n   bpf_fd_htab_map_update_elem+0x131/0x270\n   htab_map_update_elem+0x50f/0xa80\n   bpf_fd_htab_map_update_elem+0x131/0x270\n   bpf_map_update_value+0x266/0x380\n   __sys_bpf+0x21bb/0x36b0\n   __x64_sys_bpf+0x45/0x60\n   x64_sys_call+0x1b2a/0x20d0\n   do_syscall_64+0x5d/0x100\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nOne way to fix the lockdep warning is using raw_spinlock_t for\nmap_idr_lock as well. However, bpf_map_alloc_id() invokes\nidr_alloc_cyclic() after acquiring map_idr_lock, it will trigger a\nsimilar lockdep warning because the slab\u0026apos;s lock (s-\u0026gt;cpu_slab-\u0026gt;lock) is\nstill a spinlock.\n\nInstead of changing map_idr_lock\u0026apos;s type, fix the issue by invoking\nhtab_put_fd_value() after htab_unlock_bucket(). However, only deferring\nthe invocation of htab_put_fd_value() is not enough, because the old map\npointers in htab of maps can not be saved during batched deletion.\nTherefore, also defer the invocation of free_htab_elem(), so these\nto-be-freed elements could be linked together similar to lru map.\n\nThere are four callers for -\u0026gt;map_fd_put_ptr:\n\n(1) alloc_htab_elem() (through htab_put_fd_value())\nIt invokes -\u0026gt;map_fd_put_ptr() under a raw_spinlock_t. The invocation of\nhtab_put_fd_value() can not simply move after htab_unlock_bucket(),\nbecause the old element has already been stashed in htab-\u0026gt;extra_elems.\nIt may be reused immediately after htab_unlock_bucket() and the\ninvocation of htab_put_fd_value() after htab_unlock_bucket() may release\nthe newly-added element incorrectly. Therefore, saving the map pointer\nof the old element for htab of maps before unlocking the bucket and\nreleasing the map_ptr after unlock. Beside the map pointer in the old\nelement, should do the same thing for the special fields in the old\nelement as well.\n\n(2) free_htab_elem() (through htab_put_fd_value())\nIts caller includes __htab_map_lookup_and_delete_elem(),\nhtab_map_delete_elem() and __htab_map_lookup_and_delete_batch().\n\nFor htab_map_delete_elem(), simply invoke free_htab_elem() after\nhtab_unlock_bucket(). For __htab_map_lookup_and_delete_batch(), just\nlike lru map, linking the to-be-freed element into node_to_free list\nand invoking free_htab_elem() for these element after unlock. It is safe\nto reuse batch_flink as the link for node_to_free, because these\nelements have been removed from the hash llist.\n\nBecause htab of maps doesn\u0026apos;t support lookup_and_delete operation,\n__htab_map_lookup_and_delete_elem() doesn\u0026apos;t have the problem, so kept\nit as\n---truncated---(CVE-2024-56592)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: set the right AMDGPU sg segment limitation\n\nThe driver needs to set the correct max_segment_size;\notherwise debug_dma_map_sg() will complain about the\nover-mapping of the AMDGPU sg length as following:\n\nWARNING: CPU: 6 PID: 1964 at kernel/dma/debug.c:1178 debug_dma_map_sg+0x2dc/0x370\n[  364.049444] Modules linked in: veth amdgpu(OE) amdxcp drm_exec gpu_sched drm_buddy drm_ttm_helper ttm(OE) drm_suballoc_helper drm_display_helper drm_kms_helper i2c_algo_bit rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace netfs xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo iptable_nat xt_addrtype iptable_filter br_netfilter nvme_fabrics overlay nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge stp llc amd_atl intel_rapl_msr intel_rapl_common sunrpc sch_fq_codel snd_hda_codec_realtek snd_hda_codec_generic snd_hda_scodec_component snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg edac_mce_amd binfmt_misc snd_hda_codec snd_pci_acp6x snd_hda_core snd_acp_config snd_hwdep snd_soc_acpi kvm_amd snd_pcm kvm snd_seq_midi snd_seq_midi_event crct10dif_pclmul ghash_clmulni_intel sha512_ssse3 snd_rawmidi sha256_ssse3 sha1_ssse3 aesni_intel snd_seq nls_iso8859_1 crypto_simd snd_seq_device cryptd snd_timer rapl input_leds snd\n[  364.049532]  ipmi_devintf wmi_bmof ccp serio_raw k10temp sp5100_tco soundcore ipmi_msghandler cm32181 industrialio mac_hid msr parport_pc ppdev lp parport drm efi_pstore ip_tables x_tables pci_stub crc32_pclmul nvme ahci libahci i2c_piix4 r8169 nvme_core i2c_designware_pci realtek i2c_ccgx_ucsi video wmi hid_generic cdc_ether usbnet usbhid hid r8152 mii\n[  364.049576] CPU: 6 PID: 1964 Comm: rocminfo Tainted: G           OE      6.10.0-custom #492\n[  364.049579] Hardware name: AMD Majolica-RN/Majolica-RN, BIOS RMJ1009A 06/13/2021\n[  364.049582] RIP: 0010:debug_dma_map_sg+0x2dc/0x370\n[  364.049585] Code: 89 4d b8 e8 36 b1 86 00 8b 4d b8 48 8b 55 b0 44 8b 45 a8 4c 8b 4d a0 48 89 c6 48 c7 c7 00 4b 74 bc 4c 89 4d b8 e8 b4 73 f3 ff \u0026lt;0f\u0026gt; 0b 4c 8b 4d b8 8b 15 c8 2c b8 01 85 d2 0f 85 ee fd ff ff 8b 05\n[  364.049588] RSP: 0018:ffff9ca600b57ac0 EFLAGS: 00010286\n[  364.049590] RAX: 0000000000000000 RBX: ffff88b7c132b0c8 RCX: 0000000000000027\n[  364.049592] RDX: ffff88bb0f521688 RSI: 0000000000000001 RDI: ffff88bb0f521680\n[  364.049594] RBP: ffff9ca600b57b20 R08: 000000000000006f R09: ffff9ca600b57930\n[  364.049596] R10: ffff9ca600b57928 R11: ffffffffbcb46328 R12: 0000000000000000\n[  364.049597] R13: 0000000000000001 R14: ffff88b7c19c0700 R15: ffff88b7c9059800\n[  364.049599] FS:  00007fb2d3516e80(0000) GS:ffff88bb0f500000(0000) knlGS:0000000000000000\n[  364.049601] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  364.049603] CR2: 000055610bd03598 CR3: 00000001049f6000 CR4: 0000000000350ef0\n[  364.049605] Call Trace:\n[  364.049607]  \u0026lt;TASK\u0026gt;\n[  364.049609]  ? show_regs+0x6d/0x80\n[  364.049614]  ? __warn+0x8c/0x140\n[  364.049618]  ? debug_dma_map_sg+0x2dc/0x370\n[  364.049621]  ? report_bug+0x193/0x1a0\n[  364.049627]  ? handle_bug+0x46/0x80\n[  364.049631]  ? exc_invalid_op+0x1d/0x80\n[  364.049635]  ? asm_exc_invalid_op+0x1f/0x30\n[  364.049642]  ? debug_dma_map_sg+0x2dc/0x370\n[  364.049647]  __dma_map_sg_attrs+0x90/0xe0\n[  364.049651]  dma_map_sgtable+0x25/0x40\n[  364.049654]  amdgpu_bo_move+0x59a/0x850 [amdgpu]\n[  364.049935]  ? srso_return_thunk+0x5/0x5f\n[  364.049939]  ? amdgpu_ttm_tt_populate+0x5d/0xc0 [amdgpu]\n[  364.050095]  ttm_bo_handle_move_mem+0xc3/0x180 [ttm]\n[  364.050103]  ttm_bo_validate+0xc1/0x160 [ttm]\n[  364.050108]  ? amdgpu_ttm_tt_get_user_pages+0xe5/0x1b0 [amdgpu]\n[  364.050263]  amdgpu_amdkfd_gpuvm_alloc_memory_of_gpu+0xa12/0xc90 [amdgpu]\n[  364.050473]  kfd_ioctl_alloc_memory_of_gpu+0x16b/0x3b0 [amdgpu]\n[  364.050680]  kfd_ioctl+0x3c2/0x530 [amdgpu]\n[  364.050866]  ? __pfx_kfd_ioctl_alloc_memory_of_gpu+0x10/0x10 [amdgpu]\n[  364.05105\n---truncated---(CVE-2024-56594)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njfs: add a check to prevent array-index-out-of-bounds in dbAdjTree\n\nWhen the value of lp is 0 at the beginning of the for loop, it will\nbecome negative in the next assignment and we should bail out.(CVE-2024-56595)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njfs: fix array-index-out-of-bounds in jfs_readdir\n\nThe stbl might contain some invalid values. Added a check to\nreturn error code in that case.(CVE-2024-56596)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njfs: fix shift-out-of-bounds in dbSplit\n\nWhen dmt_budmin is less than zero, it causes errors\nin the later stages. Added a check to return an error beforehand\nin dbAllocCtl itself.(CVE-2024-56597)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create()\n\nbt_sock_alloc() allocates the sk object and attaches it to the provided\nsock object. On error l2cap_sock_alloc() frees the sk object, but the\ndangling pointer is still attached to the sock object, which may create\nuse-after-free in other code.(CVE-2024-56605)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtw88: use ieee80211_purge_tx_queue() to purge TX skb\n\nWhen removing kernel modules by:\n   rmmod rtw88_8723cs rtw88_8703b rtw88_8723x rtw88_sdio rtw88_core\n\nDriver uses skb_queue_purge() to purge TX skb, but not report tx status\ncausing \u0026quot;Have pending ack frames!\u0026quot; warning. Use ieee80211_purge_tx_queue()\nto correct this.\n\nSince ieee80211_purge_tx_queue() doesn\u0026apos;t take locks, to prevent racing\nbetween TX work and purge TX queue, flush and destroy TX work in advance.\n\n   wlan0: deauthenticating from aa:f5:fd:60:4c:a8 by local\n     choice (Reason: 3=DEAUTH_LEAVING)\n   ------------[ cut here ]------------\n   Have pending ack frames!\n   WARNING: CPU: 3 PID: 9232 at net/mac80211/main.c:1691\n       ieee80211_free_ack_frame+0x5c/0x90 [mac80211]\n   CPU: 3 PID: 9232 Comm: rmmod Tainted: G         C\n       6.10.1-200.fc40.aarch64 #1\n   Hardware name: pine64 Pine64 PinePhone Braveheart\n      (1.1)/Pine64 PinePhone Braveheart (1.1), BIOS 2024.01 01/01/2024\n   pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n   pc : ieee80211_free_ack_frame+0x5c/0x90 [mac80211]\n   lr : ieee80211_free_ack_frame+0x5c/0x90 [mac80211]\n   sp : ffff80008c1b37b0\n   x29: ffff80008c1b37b0 x28: ffff000003be8000 x27: 0000000000000000\n   x26: 0000000000000000 x25: ffff000003dc14b8 x24: ffff80008c1b37d0\n   x23: ffff000000ff9f80 x22: 0000000000000000 x21: 000000007fffffff\n   x20: ffff80007c7e93d8 x19: ffff00006e66f400 x18: 0000000000000000\n   x17: ffff7ffffd2b3000 x16: ffff800083fc0000 x15: 0000000000000000\n   x14: 0000000000000000 x13: 2173656d61726620 x12: 6b636120676e6964\n   x11: 0000000000000000 x10: 000000000000005d x9 : ffff8000802af2b0\n   x8 : ffff80008c1b3430 x7 : 0000000000000001 x6 : 0000000000000001\n   x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000\n   x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000003be8000\n   Call trace:\n    ieee80211_free_ack_frame+0x5c/0x90 [mac80211]\n    idr_for_each+0x74/0x110\n    ieee80211_free_hw+0x44/0xe8 [mac80211]\n    rtw_sdio_remove+0x9c/0xc0 [rtw88_sdio]\n    sdio_bus_remove+0x44/0x180\n    device_remove+0x54/0x90\n    device_release_driver_internal+0x1d4/0x238\n    driver_detach+0x54/0xc0\n    bus_remove_driver+0x78/0x108\n    driver_unregister+0x38/0x78\n    sdio_unregister_driver+0x2c/0x40\n    rtw_8723cs_driver_exit+0x18/0x1000 [rtw88_8723cs]\n    __do_sys_delete_module.isra.0+0x190/0x338\n    __arm64_sys_delete_module+0x1c/0x30\n    invoke_syscall+0x74/0x100\n    el0_svc_common.constprop.0+0x48/0xf0\n    do_el0_svc+0x24/0x38\n    el0_svc+0x3c/0x158\n    el0t_64_sync_handler+0x120/0x138\n    el0t_64_sync+0x194/0x198\n   ---[ end trace 0000000000000000 ]---(CVE-2024-56609)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/numa: fix memory leak due to the overwritten vma-\u0026gt;numab_state\n\n[Problem Description]\nWhen running the hackbench program of LTP, the following memory leak is\nreported by kmemleak.\n\n  # /opt/ltp/testcases/bin/hackbench 20 thread 1000\n  Running with 20*40 (== 800) tasks.\n\n  # dmesg | grep kmemleak\n  ...\n  kmemleak: 480 new suspected memory leaks (see /sys/kernel/debug/kmemleak)\n  kmemleak: 665 new suspected memory leaks (see /sys/kernel/debug/kmemleak)\n\n  # cat /sys/kernel/debug/kmemleak\n  unreferenced object 0xffff888cd8ca2c40 (size 64):\n    comm \u0026quot;hackbench\u0026quot;, pid 17142, jiffies 4299780315\n    hex dump (first 32 bytes):\n      ac 74 49 00 01 00 00 00 4c 84 49 00 01 00 00 00  .tI.....L.I.....\n      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n    backtrace (crc bff18fd4):\n      [\u0026lt;ffffffff81419a89\u0026gt;] __kmalloc_cache_noprof+0x2f9/0x3f0\n      [\u0026lt;ffffffff8113f715\u0026gt;] task_numa_work+0x725/0xa00\n      [\u0026lt;ffffffff8110f878\u0026gt;] task_work_run+0x58/0x90\n      [\u0026lt;ffffffff81ddd9f8\u0026gt;] syscall_exit_to_user_mode+0x1c8/0x1e0\n      [\u0026lt;ffffffff81dd78d5\u0026gt;] do_syscall_64+0x85/0x150\n      [\u0026lt;ffffffff81e0012b\u0026gt;] entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  ...\n\nThis issue can be consistently reproduced on three different servers:\n  * a 448-core server\n  * a 256-core server\n  * a 192-core server\n\n[Root Cause]\nSince multiple threads are created by the hackbench program (along with\nthe command argument \u0026apos;thread\u0026apos;), a shared vma might be accessed by two or\nmore cores simultaneously. When two or more cores observe that\nvma-\u0026gt;numab_state is NULL at the same time, vma-\u0026gt;numab_state will be\noverwritten.\n\nAlthough current code ensures that only one thread scans the VMAs in a\nsingle \u0026apos;numa_scan_period\u0026apos;, there might be a chance for another thread\nto enter in the next \u0026apos;numa_scan_period\u0026apos; while we have not gotten till\nnumab_state allocation [1].\n\nNote that the command `/opt/ltp/testcases/bin/hackbench 50 process 1000`\ncannot the reproduce the issue. It is verified with 200+ test runs.\n\n[Solution]\nUse the cmpxchg atomic operation to ensure that only one thread executes\nthe vma-\u0026gt;numab_state assignment.\n\n[1] https://lore.kernel.org/lkml/1794be3c-358c-4cdc-a43d-a1f841d91ef7@amd.com/(CVE-2024-56613)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnilfs2: fix potential out-of-bounds memory access in nilfs_find_entry()\n\nSyzbot reported that when searching for records in a directory where the\ninode\u0026apos;s i_size is corrupted and has a large value, memory access outside\nthe folio/page range may occur, or a use-after-free bug may be detected if\nKASAN is enabled.\n\nThis is because nilfs_last_byte(), which is called by nilfs_find_entry()\nand others to calculate the number of valid bytes of directory data in a\npage from i_size and the page index, loses the upper 32 bits of the 64-bit\nsize information due to an inappropriate type of local variable to which\nthe i_size value is assigned.\n\nThis caused a large byte offset value due to underflow in the end address\ncalculation in the calling nilfs_find_entry(), resulting in memory access\nthat exceeds the folio/page size.\n\nFix this issue by changing the type of the local variable causing the bit\nloss from \u0026quot;unsigned int\u0026quot; to \u0026quot;u64\u0026quot;.  The return value of nilfs_last_byte()\nis also of type \u0026quot;unsigned int\u0026quot;, but it is truncated so as not to exceed\nPAGE_SIZE and no bit loss occurs, so no change is required.(CVE-2024-56619)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: ufs: core: sysfs: Prevent div by zero\n\nPrevent a division by 0 when monitoring is not enabled.(CVE-2024-56622)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix Out-of-Bounds Write in ksmbd_vfs_stream_write\n\nAn offset from client could be a negative value, It could allows\nto write data outside the bounds of the allocated buffer.\nNote that this issue is coming when setting\n\u0026apos;vfs objects = streams_xattr parameter\u0026apos; in ksmbd.conf..(CVE-2024-56626)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: sg: Fix slab-use-after-free read in sg_release()\n\nFix a use-after-free bug in sg_release(), detected by syzbot with KASAN:\n\nBUG: KASAN: slab-use-after-free in lock_release+0x151/0xa30\nkernel/locking/lockdep.c:5838\n__mutex_unlock_slowpath+0xe2/0x750 kernel/locking/mutex.c:912\nsg_release+0x1f4/0x2e0 drivers/scsi/sg.c:407\n\nIn sg_release(), the function kref_put(\u0026amp;sfp-\u0026gt;f_ref, sg_remove_sfp) is\ncalled before releasing the open_rel_lock mutex. The kref_put() call may\ndecrement the reference count of sfp to zero, triggering its cleanup\nthrough sg_remove_sfp(). This cleanup includes scheduling deferred work\nvia sg_remove_sfp_usercontext(), which ultimately frees sfp.\n\nAfter kref_put(), sg_release() continues to unlock open_rel_lock and may\nreference sfp or sdp. If sfp has already been freed, this results in a\nslab-use-after-free error.\n\nMove the kref_put(\u0026amp;sfp-\u0026gt;f_ref, sg_remove_sfp) call after unlocking the\nopen_rel_lock mutex. This ensures:\n\n - No references to sfp or sdp occur after the reference count is\n   decremented.\n\n - Cleanup functions such as sg_remove_sfp() and\n   sg_remove_sfp_usercontext() can safely execute without impacting the\n   mutex handling in sg_release().\n\nThe fix has been tested and validated by syzbot. This patch closes the\nbug reported at the following syzkaller link and ensures proper\nsequencing of resource cleanup and mutex operations, eliminating the\nrisk of use-after-free errors in sg_release().(CVE-2024-56631)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg\n\nThe current sk memory accounting logic in __SK_REDIRECT is pre-uncharging\ntosend bytes, which is either msg-\u0026gt;sg.size or a smaller value apply_bytes.\n\nPotential problems with this strategy are as follows:\n\n- If the actual sent bytes are smaller than tosend, we need to charge some\n  bytes back, as in line 487, which is okay but seems not clean.\n\n- When tosend is set to apply_bytes, as in line 417, and (ret \u0026lt; 0), we may\n  miss uncharging (msg-\u0026gt;sg.size - apply_bytes) bytes.\n\n[...]\n415 tosend = msg-\u0026gt;sg.size;\n416 if (psock-\u0026gt;apply_bytes \u0026amp;\u0026amp; psock-\u0026gt;apply_bytes \u0026lt; tosend)\n417   tosend = psock-\u0026gt;apply_bytes;\n[...]\n443 sk_msg_return(sk, msg, tosend);\n444 release_sock(sk);\n446 origsize = msg-\u0026gt;sg.size;\n447 ret = tcp_bpf_sendmsg_redir(sk_redir, redir_ingress,\n448                             msg, tosend, flags);\n449 sent = origsize - msg-\u0026gt;sg.size;\n[...]\n454 lock_sock(sk);\n455 if (unlikely(ret \u0026lt; 0)) {\n456   int free = sk_msg_free_nocharge(sk, msg);\n458   if (!cork)\n459     *copied -= free;\n460 }\n[...]\n487 if (eval == __SK_REDIRECT)\n488   sk_mem_charge(sk, tosend - sent);\n[...]\n\nWhen running the selftest test_txmsg_redir_wait_sndmem with txmsg_apply,\nthe following warning will be reported:\n\n------------[ cut here ]------------\nWARNING: CPU: 6 PID: 57 at net/ipv4/af_inet.c:156 inet_sock_destruct+0x190/0x1a0\nModules linked in:\nCPU: 6 UID: 0 PID: 57 Comm: kworker/6:0 Not tainted 6.12.0-rc1.bm.1-amd64+ #43\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nWorkqueue: events sk_psock_destroy\nRIP: 0010:inet_sock_destruct+0x190/0x1a0\nRSP: 0018:ffffad0a8021fe08 EFLAGS: 00010206\nRAX: 0000000000000011 RBX: ffff9aab4475b900 RCX: ffff9aab481a0800\nRDX: 0000000000000303 RSI: 0000000000000011 RDI: ffff9aab4475b900\nRBP: ffff9aab4475b990 R08: 0000000000000000 R09: ffff9aab40050ec0\nR10: 0000000000000000 R11: ffff9aae6fdb1d01 R12: ffff9aab49c60400\nR13: ffff9aab49c60598 R14: ffff9aab49c60598 R15: dead000000000100\nFS:  0000000000000000(0000) GS:ffff9aae6fd80000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007ffec7e47bd8 CR3: 00000001a1a1c004 CR4: 0000000000770ef0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n\u0026lt;TASK\u0026gt;\n? __warn+0x89/0x130\n? inet_sock_destruct+0x190/0x1a0\n? report_bug+0xfc/0x1e0\n? handle_bug+0x5c/0xa0\n? exc_invalid_op+0x17/0x70\n? asm_exc_invalid_op+0x1a/0x20\n? inet_sock_destruct+0x190/0x1a0\n__sk_destruct+0x25/0x220\nsk_psock_destroy+0x2b2/0x310\nprocess_scheduled_works+0xa3/0x3e0\nworker_thread+0x117/0x240\n? __pfx_worker_thread+0x10/0x10\nkthread+0xcf/0x100\n? __pfx_kthread+0x10/0x10\nret_from_fork+0x31/0x40\n? __pfx_kthread+0x10/0x10\nret_from_fork_asm+0x1a/0x30\n\u0026lt;/TASK\u0026gt;\n---[ end trace 0000000000000000 ]---\n\nIn __SK_REDIRECT, a more concise way is delaying the uncharging after sent\nbytes are finalized, and uncharge this value. When (ret \u0026lt; 0), we shall\ninvoke sk_msg_free.\n\nSame thing happens in case __SK_DROP, when tosend is set to apply_bytes,\nwe may miss uncharging (msg-\u0026gt;sg.size - apply_bytes) bytes. The same\nwarning will be reported in selftest.\n\n[...]\n468 case __SK_DROP:\n469 default:\n470 sk_msg_free_partial(sk, msg, tosend);\n471 sk_msg_apply_bytes(psock, tosend);\n472 *copied -= (tosend + delta);\n473 return -EACCES;\n[...]\n\nSo instead of sk_msg_free_partial we can do sk_msg_free here.(CVE-2024-56633)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_inner: incorrect percpu area handling under softirq\n\nSoftirq can interrupt ongoing packet from process context that is\nwalking over the percpu area that contains inner header offsets.\n\nDisable bh and perform three checks before restoring the percpu inner\nheader offsets to validate that the percpu area is valid for this\nskbuff:\n\n1) If the NFT_PKTINFO_INNER_FULL flag is set on, then this skbuff\n   has already been parsed before for inner header fetching to\n   register.\n\n2) Validate that the percpu area refers to this skbuff using the\n   skbuff pointer as a cookie. If there is a cookie mismatch, then\n   this skbuff needs to be parsed again.\n\n3) Finally, validate if the percpu area refers to this tunnel type.\n\nOnly after these three checks the percpu area is restored to a on-stack\ncopy and bh is enabled again.\n\nAfter inner header fetching, the on-stack copy is stored back to the\npercpu area.(CVE-2024-56638)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: enetc: Do not configure preemptible TCs if SIs do not support\n\nBoth ENETC PF and VF drivers share enetc_setup_tc_mqprio() to configure\nMQPRIO. And enetc_setup_tc_mqprio() calls enetc_change_preemptible_tcs()\nto configure preemptible TCs. However, only PF is able to configure\npreemptible TCs. Because only PF has related registers, while VF does not\nhave these registers. So for VF, its hw-\u0026gt;port pointer is NULL. Therefore,\nVF will access an invalid pointer when accessing a non-existent register,\nwhich will cause a crash issue. The simplified log is as follows.\n\nroot@ls1028ardb:~# tc qdisc add dev eno0vf0 parent root handle 100: \\\nmqprio num_tc 4 map 0 0 1 1 2 2 3 3 queues 1@0 1@1 1@2 1@3 hw 1\n[  187.290775] Unable to handle kernel paging request at virtual address 0000000000001f00\n[  187.424831] pc : enetc_mm_commit_preemptible_tcs+0x1c4/0x400\n[  187.430518] lr : enetc_mm_commit_preemptible_tcs+0x30c/0x400\n[  187.511140] Call trace:\n[  187.513588]  enetc_mm_commit_preemptible_tcs+0x1c4/0x400\n[  187.518918]  enetc_setup_tc_mqprio+0x180/0x214\n[  187.523374]  enetc_vf_setup_tc+0x1c/0x30\n[  187.527306]  mqprio_enable_offload+0x144/0x178\n[  187.531766]  mqprio_init+0x3ec/0x668\n[  187.535351]  qdisc_create+0x15c/0x488\n[  187.539023]  tc_modify_qdisc+0x398/0x73c\n[  187.542958]  rtnetlink_rcv_msg+0x128/0x378\n[  187.547064]  netlink_rcv_skb+0x60/0x130\n[  187.550910]  rtnetlink_rcv+0x18/0x24\n[  187.554492]  netlink_unicast+0x300/0x36c\n[  187.558425]  netlink_sendmsg+0x1a8/0x420\n[  187.606759] ---[ end trace 0000000000000000 ]---\n\nIn addition, some PFs also do not support configuring preemptible TCs,\nsuch as eno1 and eno3 on LS1028A. It won\u0026apos;t crash like it does for VFs,\nbut we should prevent these PFs from accessing these unimplemented\nregisters.(CVE-2024-56649)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: Fix using rcu_read_(un)lock while iterating\n\nThe usage of rcu_read_(un)lock while inside list_for_each_entry_rcu is\nnot safe since for the most part entries fetched this way shall be\ntreated as rcu_dereference:\n\n\tNote that the value returned by rcu_dereference() is valid\n\tonly within the enclosing RCU read-side critical section [1]_.\n\tFor example, the following is **not** legal::\n\n\t\trcu_read_lock();\n\t\tp = rcu_dereference(head.next);\n\t\trcu_read_unlock();\n\t\tx = p-\u0026gt;address;\t/* BUG!!! */\n\t\trcu_read_lock();\n\t\ty = p-\u0026gt;data;\t/* BUG!!! */\n\t\trcu_read_unlock();(CVE-2024-56654)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: DR, prevent potential error pointer dereference\n\nThe dr_domain_add_vport_cap() function generally returns NULL on error\nbut sometimes we want it to return ERR_PTR(-EBUSY) so the caller can\nretry.  The problem here is that \u0026quot;ret\u0026quot; can be either -EBUSY or -ENOMEM\nand if it\u0026apos;s and -ENOMEM then the error pointer is propogated back and\neventually dereferenced in dr_ste_v0_build_src_gvmi_qpn_tag().(CVE-2024-56660)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nacpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl\n\nFix an issue detected by syzbot with KASAN:\n\nBUG: KASAN: vmalloc-out-of-bounds in cmd_to_func drivers/acpi/nfit/\ncore.c:416 [inline]\nBUG: KASAN: vmalloc-out-of-bounds in acpi_nfit_ctl+0x20e8/0x24a0\ndrivers/acpi/nfit/core.c:459\n\nThe issue occurs in cmd_to_func when the call_pkg-\u0026gt;nd_reserved2\narray is accessed without verifying that call_pkg points to a buffer\nthat is appropriately sized as a struct nd_cmd_pkg. This can lead\nto out-of-bounds access and undefined behavior if the buffer does not\nhave sufficient space.\n\nTo address this, a check was added in acpi_nfit_ctl() to ensure that\nbuf is not NULL and that buf_len is less than sizeof(*call_pkg)\nbefore accessing it. This ensures safe access to the members of\ncall_pkg, including the nd_reserved2 array.(CVE-2024-56662)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: nl80211: fix NL80211_ATTR_MLO_LINK_ID off-by-one\n\nSince the netlink attribute range validation provides inclusive\nchecking, the *max* of attribute NL80211_ATTR_MLO_LINK_ID should be\nIEEE80211_MLD_MAX_NUM_LINKS - 1 otherwise causing an off-by-one.\n\nOne crash stack for demonstration:\n==================================================================\nBUG: KASAN: wild-memory-access in ieee80211_tx_control_port+0x3b6/0xca0 net/mac80211/tx.c:5939\nRead of size 6 at addr 001102080000000c by task fuzzer.386/9508\n\nCPU: 1 PID: 9508 Comm: syz.1.386 Not tainted 6.1.70 #2\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:88 [inline]\n dump_stack_lvl+0x177/0x231 lib/dump_stack.c:106\n print_report+0xe0/0x750 mm/kasan/report.c:398\n kasan_report+0x139/0x170 mm/kasan/report.c:495\n kasan_check_range+0x287/0x290 mm/kasan/generic.c:189\n memcpy+0x25/0x60 mm/kasan/shadow.c:65\n ieee80211_tx_control_port+0x3b6/0xca0 net/mac80211/tx.c:5939\n rdev_tx_control_port net/wireless/rdev-ops.h:761 [inline]\n nl80211_tx_control_port+0x7b3/0xc40 net/wireless/nl80211.c:15453\n genl_family_rcv_msg_doit+0x22e/0x320 net/netlink/genetlink.c:756\n genl_family_rcv_msg net/netlink/genetlink.c:833 [inline]\n genl_rcv_msg+0x539/0x740 net/netlink/genetlink.c:850\n netlink_rcv_skb+0x1de/0x420 net/netlink/af_netlink.c:2508\n genl_rcv+0x24/0x40 net/netlink/genetlink.c:861\n netlink_unicast_kernel net/netlink/af_netlink.c:1326 [inline]\n netlink_unicast+0x74b/0x8c0 net/netlink/af_netlink.c:1352\n netlink_sendmsg+0x882/0xb90 net/netlink/af_netlink.c:1874\n sock_sendmsg_nosec net/socket.c:716 [inline]\n __sock_sendmsg net/socket.c:728 [inline]\n ____sys_sendmsg+0x5cc/0x8f0 net/socket.c:2499\n ___sys_sendmsg+0x21c/0x290 net/socket.c:2553\n __sys_sendmsg net/socket.c:2582 [inline]\n __do_sys_sendmsg net/socket.c:2591 [inline]\n __se_sys_sendmsg+0x19e/0x270 net/socket.c:2589\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x45/0x90 arch/x86/entry/common.c:81\n entry_SYSCALL_64_after_hwframe+0x63/0xcd\n\nUpdate the policy to ensure correct validation.(CVE-2024-56663)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915: Fix NULL pointer dereference in capture_engine\n\nWhen the intel_context structure contains NULL,\nit raises a NULL pointer dereference error in drm_info().\n\n(cherry picked from commit 754302a5bc1bd8fd3b7d85c168b0a1af6d4bba4d)(CVE-2024-56667)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblk-cgroup: Fix UAF in blkcg_unpin_online()\n\nblkcg_unpin_online() walks up the blkcg hierarchy putting the online pin. To\nwalk up, it uses blkcg_parent(blkcg) but it was calling that after\nblkcg_destroy_blkgs(blkcg) which could free the blkcg, leading to the\nfollowing UAF:\n\n  ==================================================================\n  BUG: KASAN: slab-use-after-free in blkcg_unpin_online+0x15a/0x270\n  Read of size 8 at addr ffff8881057678c0 by task kworker/9:1/117\n\n  CPU: 9 UID: 0 PID: 117 Comm: kworker/9:1 Not tainted 6.13.0-rc1-work-00182-gb8f52214c61a-dirty #48\n  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS unknown 02/02/2022\n  Workqueue: cgwb_release cgwb_release_workfn\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x27/0x80\n   print_report+0x151/0x710\n   kasan_report+0xc0/0x100\n   blkcg_unpin_online+0x15a/0x270\n   cgwb_release_workfn+0x194/0x480\n   process_scheduled_works+0x71b/0xe20\n   worker_thread+0x82a/0xbd0\n   kthread+0x242/0x2c0\n   ret_from_fork+0x33/0x70\n   ret_from_fork_asm+0x1a/0x30\n   \u0026lt;/TASK\u0026gt;\n  ...\n  Freed by task 1944:\n   kasan_save_track+0x2b/0x70\n   kasan_save_free_info+0x3c/0x50\n   __kasan_slab_free+0x33/0x50\n   kfree+0x10c/0x330\n   css_free_rwork_fn+0xe6/0xb30\n   process_scheduled_works+0x71b/0xe20\n   worker_thread+0x82a/0xbd0\n   kthread+0x242/0x2c0\n   ret_from_fork+0x33/0x70\n   ret_from_fork_asm+0x1a/0x30\n\nNote that the UAF is not easy to trigger as the free path is indirected\nbehind a couple RCU grace periods and a work item execution. I could only\ntrigger it with artifical msleep() injected in blkcg_unpin_online().\n\nFix it by reading the parent pointer before destroying the blkcg\u0026apos;s blkg\u0026apos;s.(CVE-2024-56672)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nocteontx2-pf: handle otx2_mbox_get_rsp errors in otx2_common.c\n\nAdd error pointer check after calling otx2_mbox_get_rsp().(CVE-2024-56679)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmfd: intel_soc_pmic_bxtwc: Use IRQ domain for USB Type-C device\n\nWhile design wise the idea of converting the driver to use\nthe hierarchy of the IRQ chips is correct, the implementation\nhas (inherited) flaws. This was unveiled when platform_get_irq()\nhad started WARN() on IRQ 0 that is supposed to be a Linux\nIRQ number (also known as vIRQ).\n\nRework the driver to respect IRQ domain when creating each MFD\ndevice separately, as the domain is not the same for all of them.(CVE-2024-56691)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf, sockmap: Several fixes to bpf_msg_pop_data\n\nSeveral fixes to bpf_msg_pop_data,\n1. In sk_msg_shift_left, we should put_page\n2. if (len == 0), return early is better\n3. pop the entire sk_msg (last == msg-\u0026gt;sg.size) should be supported\n4. Fix for the value of variable \u0026quot;a\u0026quot;\n5. In sk_msg_shift_left, after shifting, i has already pointed to the next\nelement. Addtional sk_msg_iter_var_next may result in BUG.(CVE-2024-56720)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nocteontx2-pf: handle otx2_mbox_get_rsp errors in cn10k.c\n\nAdd error pointer check after calling otx2_mbox_get_rsp().(CVE-2024-56726)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nrtc: check if __rtc_read_time was successful in rtc_timer_do_work()\n\nIf the __rtc_read_time call fails,, the struct rtc_time tm; may contain\nuninitialized data, or an illegal date/time read from the RTC hardware.\n\nWhen calling rtc_tm_to_ktime later, the result may be a very large value\n(possibly KTIME_MAX). If there are periodic timers in rtc-\u0026gt;timerqueue,\nthey will continually expire, may causing kernel softlockup.(CVE-2024-56739)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvfio/mlx5: Fix an unwind issue in mlx5vf_add_migration_pages()\n\nFix an unwind issue in mlx5vf_add_migration_pages().\n\nIf a set of pages is allocated but fails to be added to the SG table,\nthey need to be freed to prevent a memory leak.\n\nAny pages successfully added to the SG table will be freed as part of\nmlx5vf_free_data_buffer().(CVE-2024-56742)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: Fix reset_method_store() memory leak\n\nIn reset_method_store(), a string is allocated via kstrndup() and assigned\nto the local \u0026quot;options\u0026quot;. options is then used in with strsep() to find\nspaces:\n\n  while ((name = strsep(\u0026amp;options, \u0026quot; \u0026quot;)) != NULL) {\n\nIf there are no remaining spaces, then options is set to NULL by strsep(),\nso the subsequent kfree(options) doesn\u0026apos;t free the memory allocated via\nkstrndup().\n\nFix by using a separate tmp_options to iterate with strsep() so options is\npreserved.(CVE-2024-56745)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qedi: Fix a possible memory leak in qedi_alloc_and_init_sb()\n\nHook \u0026quot;qedi_ops-\u0026gt;common-\u0026gt;sb_init = qed_sb_init\u0026quot; does not release the DMA\nmemory sb_virt when it fails. Add dma_free_coherent() to free it. This\nis the same way as qedr_alloc_mem_sb() and qede_alloc_mem_sb().(CVE-2024-56747)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING\n\nIn fscache_create_volume(), there is a missing memory barrier between the\nbit-clearing operation and the wake-up operation. This may cause a\nsituation where, after a wake-up, the bit-clearing operation hasn\u0026apos;t been\ndetected yet, leading to an indefinite wait. The triggering process is as\nfollows:\n\n  [cookie1]                [cookie2]                  [volume_work]\nfscache_perform_lookup\n  fscache_create_volume\n                        fscache_perform_lookup\n                          fscache_create_volume\n\t\t\t                        fscache_create_volume_work\n                                                  cachefiles_acquire_volume\n                                                  clear_and_wake_up_bit\n    test_and_set_bit\n                            test_and_set_bit\n                              goto maybe_wait\n      goto no_wait\n\nIn the above process, cookie1 and cookie2 has the same volume. When cookie1\nenters the -no_wait- process, it will clear the bit and wake up the waiting\nprocess. If a barrier is missing, it may cause cookie2 to remain in the\n-wait- process indefinitely.\n\nIn commit 3288666c7256 (\u0026quot;fscache: Use clear_and_wake_up_bit() in\nfscache_create_volume_work()\u0026quot;), barriers were added to similar operations\nin fscache_create_volume_work(), but fscache_create_volume() was missed.\n\nBy combining the clear and wake operations into clear_and_wake_up_bit() to\nfix this issue.(CVE-2024-56755)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-pci: fix freeing of the HMB descriptor table\n\nThe HMB descriptor table is sized to the maximum number of descriptors\nthat could be used for a given device, but __nvme_alloc_host_mem could\nbreak out of the loop earlier on memory allocation failure and end up\nusing less descriptors than planned for, which leads to an incorrect\nsize passed to dma_free_coherent.\n\nIn practice this was not showing up because the number of descriptors\ntends to be low and the dma coherent allocator always allocates and\nfrees at least a page.(CVE-2024-56756)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix use-after-free when COWing tree bock and tracing is enabled\n\nWhen a COWing a tree block, at btrfs_cow_block(), and we have the\ntracepoint trace_btrfs_cow_block() enabled and preemption is also enabled\n(CONFIG_PREEMPT=y), we can trigger a use-after-free in the COWed extent\nbuffer while inside the tracepoint code. This is because in some paths\nthat call btrfs_cow_block(), such as btrfs_search_slot(), we are holding\nthe last reference on the extent buffer @buf so btrfs_force_cow_block()\ndrops the last reference on the @buf extent buffer when it calls\nfree_extent_buffer_stale(buf), which schedules the release of the extent\nbuffer with RCU. This means that if we are on a kernel with preemption,\nthe current task may be preempted before calling trace_btrfs_cow_block()\nand the extent buffer already released by the time trace_btrfs_cow_block()\nis called, resulting in a use-after-free.\n\nFix this by moving the trace_btrfs_cow_block() from btrfs_cow_block() to\nbtrfs_force_cow_block() before the COWed extent buffer is freed.\nThis also has a side effect of invoking the tracepoint in the tree defrag\ncode, at defrag.c:btrfs_realloc_node(), since btrfs_force_cow_block() is\ncalled there, but this is fine and it was actually missing there.(CVE-2024-56759)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Prevent bad count for tracing_cpumask_write\n\nIf a large count is provided, it will trigger a warning in bitmap_parse_user.\nAlso check zero for it.(CVE-2024-56763)",
  "id": "OESA-2025-1079",
  "modified": "2026-08-06T11:08:10Z",
  "published": "2025-01-24T11:08:10Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-1079"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50191"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53050"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53128"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53150"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53155"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53157"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53158"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53159"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53160"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53171"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53180"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53187"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53190"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53191"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53194"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53196"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53203"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53213"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53215"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53218"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53219"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53224"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53229"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53231"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53234"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53239"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53241"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-55639"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56543"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56546"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56549"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56562"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56570"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56572"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56582"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56583"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56585"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56586"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56592"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56594"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56595"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56596"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56597"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56605"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56609"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56613"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56619"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56622"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56626"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56631"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56633"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56638"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56649"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56654"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56660"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56662"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56663"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56667"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56672"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56679"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56691"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56720"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56726"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56739"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56742"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56745"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56747"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56755"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56756"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56759"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56763"
    }
  ],
  "schema_version": "1.7.2",
  "severity": [
    {
      "score": "CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "kernel security update",
  "upstream": [
    "CVE-2024-50191",
    "CVE-2024-53050",
    "CVE-2024-53128",
    "CVE-2024-53150",
    "CVE-2024-53155",
    "CVE-2024-53157",
    "CVE-2024-53158",
    "CVE-2024-53159",
    "CVE-2024-53160",
    "CVE-2024-53171",
    "CVE-2024-53180",
    "CVE-2024-53187",
    "CVE-2024-53190",
    "CVE-2024-53191",
    "CVE-2024-53194",
    "CVE-2024-53196",
    "CVE-2024-53203",
    "CVE-2024-53213",
    "CVE-2024-53215",
    "CVE-2024-53218",
    "CVE-2024-53219",
    "CVE-2024-53224",
    "CVE-2024-53229",
    "CVE-2024-53231",
    "CVE-2024-53234",
    "CVE-2024-53239",
    "CVE-2024-53241",
    "CVE-2024-55639",
    "CVE-2024-56543",
    "CVE-2024-56546",
    "CVE-2024-56549",
    "CVE-2024-56562",
    "CVE-2024-56570",
    "CVE-2024-56572",
    "CVE-2024-56582",
    "CVE-2024-56583",
    "CVE-2024-56585",
    "CVE-2024-56586",
    "CVE-2024-56592",
    "CVE-2024-56594",
    "CVE-2024-56595",
    "CVE-2024-56596",
    "CVE-2024-56597",
    "CVE-2024-56605",
    "CVE-2024-56609",
    "CVE-2024-56613",
    "CVE-2024-56619",
    "CVE-2024-56622",
    "CVE-2024-56626",
    "CVE-2024-56631",
    "CVE-2024-56633",
    "CVE-2024-56638",
    "CVE-2024-56649",
    "CVE-2024-56654",
    "CVE-2024-56660",
    "CVE-2024-56662",
    "CVE-2024-56663",
    "CVE-2024-56667",
    "CVE-2024-56672",
    "CVE-2024-56679",
    "CVE-2024-56691",
    "CVE-2024-56720",
    "CVE-2024-56726",
    "CVE-2024-56739",
    "CVE-2024-56742",
    "CVE-2024-56745",
    "CVE-2024-56747",
    "CVE-2024-56755",
    "CVE-2024-56756",
    "CVE-2024-56759",
    "CVE-2024-56763"
  ]
}

OPENSUSE-SU-2024:14500-1

Vulnerability from csaf_opensuse - Published: 2024-11-15 00:00 - Updated: 2024-11-15 00:00

Summary

kernel-devel-6.11.8-1.1 on GA media

Severity

Moderate

Scope

486 vulnerabilities in this advisory, including CVE-2024-50191.

CVE-2024-50191

5.5 (Medium)


                
                  CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Recommended: 16 products

Open the full advisory

OPENSUSE-SU-2025:14705-1

Vulnerability from csaf_opensuse - Published: 2025-01-28 00:00 - Updated: 2025-01-28 00:00

Summary

kernel-devel-longterm-6.12.11-1.1 on GA media

Severity

Moderate

Scope

504 vulnerabilities in this advisory, including CVE-2024-50191.

CVE-2024-50191

5.5 (Medium)


                
                  CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Recommended: 8 products

Open the full advisory

RHSA-2025:6966

Vulnerability from csaf_redhat - Published: 2025-05-13 08:28 - Updated: 2026-09-15 05:31

Summary

Red Hat Security Advisory: kernel security update

Severity

Moderate

Scope

406 vulnerabilities in this advisory, including CVE-2024-50191.

CVE-2024-50191

A flaw was found in the Linux kernel's handling of filesystem errors. When a filesystem encounters an error and is configured to remount as read-only, the kernel's attempt to apply this setting can conflict with other filesystem operations, specifically during filesystem freezing. This conflict can lead to system instability, potentially resulting in a denial of service where the system becomes unresponsive.

5.5 (Medium)


                
                  CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Fixed: 305 products

https://access.redhat.com/errata/RHSA-2025:6966

Open the full advisory

UBUNTU-CVE-2024-50191 (CVE-2024-50191)

Vulnerability from osv_ubuntu – Published: 2024-11-08 06:15 – Updated: 2026-09-17 16:26 – Source website

Details

Severity

5.5 (Medium)


                    
                      CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

5.5 (Medium)


                    
                      CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

N/A (UNKNOWN)


                    
                      medium

References

URL

Type

	https://ubuntu.com/security/CVE-2024-50191	REPORT
	https://www.cve.org/CVERecord?id=CVE-2024-50191	REPORT
	https://git.kernel.org/linus/d3476f3dad4ad68ae5f6…	REPORT
	https://git.kernel.org/stable/c/fbb177bc1d6487cd3…	REPORT
	https://git.kernel.org/stable/c/4061e07f040a091f6…	REPORT
	https://git.kernel.org/stable/c/58c0648e4c773f5b5…	REPORT
	https://git.kernel.org/stable/c/ee77c388469116565…	REPORT
	https://git.kernel.org/stable/c/d3476f3dad4ad68ae…	REPORT
	https://ubuntu.com/security/notices/USN-7166-1	ADVISORY
	https://ubuntu.com/security/notices/USN-7166-2	ADVISORY
	https://ubuntu.com/security/notices/USN-7166-3	ADVISORY
	https://ubuntu.com/security/notices/USN-7186-1	ADVISORY
	https://ubuntu.com/security/notices/USN-7186-2	ADVISORY
	https://ubuntu.com/security/notices/USN-7194-1	ADVISORY
	https://ubuntu.com/security/notices/USN-7166-4	ADVISORY
	https://ubuntu.com/security/notices/USN-7276-1	ADVISORY
	https://ubuntu.com/security/notices/USN-7277-1	ADVISORY
	https://ubuntu.com/security/notices/USN-7310-1	ADVISORY
	https://ubuntu.com/security/notices/USN-7383-1	ADVISORY
	https://ubuntu.com/security/notices/USN-7384-1	ADVISORY
	https://ubuntu.com/security/notices/USN-7385-1	ADVISORY
	https://ubuntu.com/security/notices/USN-7386-1	ADVISORY
	https://ubuntu.com/security/notices/USN-7383-2	ADVISORY
	https://ubuntu.com/security/notices/USN-7384-2	ADVISORY
	https://ubuntu.com/security/notices/USN-7403-1	ADVISORY
	https://ubuntu.com/security/notices/USN-7451-1	ADVISORY
	https://ubuntu.com/security/notices/USN-7468-1	ADVISORY
	https://ubuntu.com/security/notices/USN-7523-1	ADVISORY
	https://ubuntu.com/security/notices/USN-7524-1	ADVISORY

JSON

To clipboard

{
  "affected": [
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "block-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "block-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "crypto-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "crypto-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "dasd-extra-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "dasd-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "fat-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "fat-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "fb-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "firewire-core-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "floppy-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "fs-core-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "fs-core-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "fs-secondary-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "fs-secondary-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "input-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "input-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "ipmi-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "ipmi-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "irda-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "irda-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "kernel-image-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "kernel-image-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-4.15.0-23-generic",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-4.15.0-23-lowlatency",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-headers-4.15.0-23",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-headers-4.15.0-23-generic",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-headers-4.15.0-23-generic-lpae",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-headers-4.15.0-23-lowlatency",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-hwe-edge-cloud-tools-4.15.0-23",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-hwe-edge-tools-4.15.0-23",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-hwe-edge-udebs-generic",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-hwe-edge-udebs-generic-lpae",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-image-4.15.0-23-generic",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-image-4.15.0-23-generic-lpae",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-image-4.15.0-23-lowlatency",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-4.15.0-23-generic",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-4.15.0-23-lowlatency",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-modules-4.15.0-23-generic",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-modules-4.15.0-23-generic-lpae",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-modules-4.15.0-23-lowlatency",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-modules-extra-4.15.0-23-generic",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-source-4.15.0",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-tools-4.15.0-23-generic",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-tools-4.15.0-23-generic-lpae",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "linux-tools-4.15.0-23-lowlatency",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "md-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "md-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "message-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "mouse-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "mouse-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "multipath-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "multipath-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "nfs-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "nfs-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "nic-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "nic-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "nic-pcmcia-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "nic-shared-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "nic-shared-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "nic-usb-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "nic-usb-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "parport-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "parport-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "pata-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "pcmcia-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "pcmcia-storage-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "plip-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "plip-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "ppp-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "ppp-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "sata-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "sata-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "scsi-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "scsi-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "serial-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "storage-core-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "storage-core-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "usb-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "usb-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "virtio-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "vlan-modules-4.15.0-23-generic-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          },
          {
            "binary_name": "vlan-modules-4.15.0-23-generic-lpae-di",
            "binary_version": "4.15.0-23.25~16.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:16.04:LTS",
        "name": "linux-hwe-edge",
        "purl": "pkg:deb/ubuntu/linux-hwe-edge@4.15.0-23.25~16.04.1?arch=source\u0026distro=xenial"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "4.8.0-28.30~16.04.1",
        "4.8.0-30.32~16.04.1",
        "4.8.0-32.34~16.04.1",
        "4.8.0-34.36~16.04.1",
        "4.10.0-14.16~16.04.1",
        "4.10.0-19.21~16.04.1",
        "4.10.0-20.22~16.04.1",
        "4.10.0-21.23~16.04.1",
        "4.10.0-22.24~16.04.1",
        "4.10.0-24.28~16.04.1",
        "4.10.0-26.30~16.04.1",
        "4.11.0-13.19~16.04.1",
        "4.11.0-14.20~16.04.1",
        "4.13.0-16.19~16.04.3",
        "4.13.0-17.20~16.04.1",
        "4.13.0-19.22~16.04.1",
        "4.13.0-21.24~16.04.1",
        "4.13.0-25.29~16.04.2",
        "4.15.0-13.14~16.04.1",
        "4.15.0-15.16~16.04.1",
        "4.15.0-20.21~16.04.1",
        "4.15.0-22.24~16.04.1",
        "4.15.0-23.25~16.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-aws-5.0-tools-5.0.0-1027",
            "binary_version": "5.0.0-1027.30"
          },
          {
            "binary_name": "linux-aws-headers-5.0.0-1027",
            "binary_version": "5.0.0-1027.30"
          },
          {
            "binary_name": "linux-buildinfo-5.0.0-1027-aws",
            "binary_version": "5.0.0-1027.30"
          },
          {
            "binary_name": "linux-cloud-tools-5.0.0-1027-aws",
            "binary_version": "5.0.0-1027.30"
          },
          {
            "binary_name": "linux-headers-5.0.0-1027-aws",
            "binary_version": "5.0.0-1027.30"
          },
          {
            "binary_name": "linux-image-5.0.0-1027-aws",
            "binary_version": "5.0.0-1027.30"
          },
          {
            "binary_name": "linux-modules-5.0.0-1027-aws",
            "binary_version": "5.0.0-1027.30"
          },
          {
            "binary_name": "linux-modules-extra-5.0.0-1027-aws",
            "binary_version": "5.0.0-1027.30"
          },
          {
            "binary_name": "linux-tools-5.0.0-1027-aws",
            "binary_version": "5.0.0-1027.30"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "linux-aws-5.0",
        "purl": "pkg:deb/ubuntu/linux-aws-5.0@5.0.0-1027.30?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.0.0-1021.24~18.04.1",
        "5.0.0-1022.25~18.04.1",
        "5.0.0-1023.26~18.04.1",
        "5.0.0-1024.27~18.04.1",
        "5.0.0-1025.28",
        "5.0.0-1027.30"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-aws-5.3-cloud-tools-5.3.0-1035",
            "binary_version": "5.3.0-1035.37"
          },
          {
            "binary_name": "linux-aws-5.3-headers-5.3.0-1035",
            "binary_version": "5.3.0-1035.37"
          },
          {
            "binary_name": "linux-aws-5.3-tools-5.3.0-1035",
            "binary_version": "5.3.0-1035.37"
          },
          {
            "binary_name": "linux-buildinfo-5.3.0-1035-aws",
            "binary_version": "5.3.0-1035.37"
          },
          {
            "binary_name": "linux-cloud-tools-5.3.0-1035-aws",
            "binary_version": "5.3.0-1035.37"
          },
          {
            "binary_name": "linux-headers-5.3.0-1035-aws",
            "binary_version": "5.3.0-1035.37"
          },
          {
            "binary_name": "linux-image-5.3.0-1035-aws",
            "binary_version": "5.3.0-1035.37"
          },
          {
            "binary_name": "linux-modules-5.3.0-1035-aws",
            "binary_version": "5.3.0-1035.37"
          },
          {
            "binary_name": "linux-modules-extra-5.3.0-1035-aws",
            "binary_version": "5.3.0-1035.37"
          },
          {
            "binary_name": "linux-tools-5.3.0-1035-aws",
            "binary_version": "5.3.0-1035.37"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "linux-aws-5.3",
        "purl": "pkg:deb/ubuntu/linux-aws-5.3@5.3.0-1035.37?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.3.0-1016.17~18.04.1",
        "5.3.0-1017.18~18.04.1",
        "5.3.0-1019.21~18.04.1",
        "5.3.0-1023.25~18.04.1",
        "5.3.0-1028.30~18.04.1",
        "5.3.0-1030.32~18.04.1",
        "5.3.0-1032.34~18.04.2",
        "5.3.0-1033.35",
        "5.3.0-1034.36",
        "5.3.0-1035.37"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-azure-cloud-tools-5.0.0-1036",
            "binary_version": "5.0.0-1036.38"
          },
          {
            "binary_name": "linux-azure-headers-5.0.0-1036",
            "binary_version": "5.0.0-1036.38"
          },
          {
            "binary_name": "linux-azure-tools-5.0.0-1036",
            "binary_version": "5.0.0-1036.38"
          },
          {
            "binary_name": "linux-buildinfo-5.0.0-1036-azure",
            "binary_version": "5.0.0-1036.38"
          },
          {
            "binary_name": "linux-cloud-tools-5.0.0-1036-azure",
            "binary_version": "5.0.0-1036.38"
          },
          {
            "binary_name": "linux-headers-5.0.0-1036-azure",
            "binary_version": "5.0.0-1036.38"
          },
          {
            "binary_name": "linux-image-unsigned-5.0.0-1036-azure",
            "binary_version": "5.0.0-1036.38"
          },
          {
            "binary_name": "linux-modules-5.0.0-1036-azure",
            "binary_version": "5.0.0-1036.38"
          },
          {
            "binary_name": "linux-modules-extra-5.0.0-1036-azure",
            "binary_version": "5.0.0-1036.38"
          },
          {
            "binary_name": "linux-tools-5.0.0-1036-azure",
            "binary_version": "5.0.0-1036.38"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "linux-azure",
        "purl": "pkg:deb/ubuntu/linux-azure@5.0.0-1036.38?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "4.15.0-1002.2",
        "4.15.0-1003.3",
        "4.15.0-1004.4",
        "4.15.0-1008.8",
        "4.15.0-1009.9",
        "4.15.0-1012.12",
        "4.15.0-1013.13",
        "4.15.0-1014.14",
        "4.15.0-1018.18",
        "4.15.0-1019.19",
        "4.15.0-1021.21",
        "4.15.0-1022.23",
        "4.15.0-1023.24",
        "4.15.0-1025.26",
        "4.15.0-1028.29",
        "4.15.0-1030.31",
        "4.15.0-1031.32",
        "4.15.0-1032.33",
        "4.15.0-1035.36",
        "4.15.0-1036.38",
        "4.15.0-1037.39",
        "4.18.0-1011.11~18.04.1",
        "4.18.0-1013.13~18.04.1",
        "4.18.0-1014.14~18.04.1",
        "4.18.0-1018.18~18.04.1",
        "4.18.0-1019.19~18.04.1",
        "4.18.0-1020.20~18.04.1",
        "4.18.0-1023.24~18.04.1",
        "4.18.0-1024.25~18.04.1",
        "4.18.0-1025.27~18.04.1",
        "5.0.0-1014.14~18.04.1",
        "5.0.0-1016.17~18.04.1",
        "5.0.0-1018.19~18.04.1",
        "5.0.0-1020.21~18.04.1",
        "5.0.0-1022.23~18.04.1",
        "5.0.0-1023.24~18.04.1",
        "5.0.0-1025.27~18.04.1",
        "5.0.0-1027.29~18.04.1",
        "5.0.0-1028.30~18.04.1",
        "5.0.0-1029.31~18.04.1",
        "5.0.0-1031.33",
        "5.0.0-1032.34",
        "5.0.0-1035.37",
        "5.0.0-1036.38"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-azure-5.3-cloud-tools-5.3.0-1035",
            "binary_version": "5.3.0-1035.36"
          },
          {
            "binary_name": "linux-azure-5.3-headers-5.3.0-1035",
            "binary_version": "5.3.0-1035.36"
          },
          {
            "binary_name": "linux-azure-5.3-tools-5.3.0-1035",
            "binary_version": "5.3.0-1035.36"
          },
          {
            "binary_name": "linux-buildinfo-5.3.0-1035-azure",
            "binary_version": "5.3.0-1035.36"
          },
          {
            "binary_name": "linux-cloud-tools-5.3.0-1035-azure",
            "binary_version": "5.3.0-1035.36"
          },
          {
            "binary_name": "linux-headers-5.3.0-1035-azure",
            "binary_version": "5.3.0-1035.36"
          },
          {
            "binary_name": "linux-image-unsigned-5.3.0-1035-azure",
            "binary_version": "5.3.0-1035.36"
          },
          {
            "binary_name": "linux-modules-5.3.0-1035-azure",
            "binary_version": "5.3.0-1035.36"
          },
          {
            "binary_name": "linux-modules-extra-5.3.0-1035-azure",
            "binary_version": "5.3.0-1035.36"
          },
          {
            "binary_name": "linux-tools-5.3.0-1035-azure",
            "binary_version": "5.3.0-1035.36"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "linux-azure-5.3",
        "purl": "pkg:deb/ubuntu/linux-azure-5.3@5.3.0-1035.36?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.3.0-1007.8~18.04.1",
        "5.3.0-1008.9~18.04.1",
        "5.3.0-1009.10~18.04.1",
        "5.3.0-1010.11~18.04.1",
        "5.3.0-1012.13~18.04.1",
        "5.3.0-1013.14~18.04.1",
        "5.3.0-1016.17~18.04.1",
        "5.3.0-1018.19~18.04.1",
        "5.3.0-1019.20~18.04.1",
        "5.3.0-1020.21~18.04.1",
        "5.3.0-1022.23~18.04.1",
        "5.3.0-1028.29~18.04.1",
        "5.3.0-1031.32~18.04.1",
        "5.3.0-1032.33~18.04.1",
        "5.3.0-1034.35~18.04.1",
        "5.3.0-1035.36"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-azure-edge-cloud-tools-5.0.0-1012",
            "binary_version": "5.0.0-1012.12~18.04.2"
          },
          {
            "binary_name": "linux-azure-edge-tools-5.0.0-1012",
            "binary_version": "5.0.0-1012.12~18.04.2"
          },
          {
            "binary_name": "linux-azure-headers-5.0.0-1012",
            "binary_version": "5.0.0-1012.12~18.04.2"
          },
          {
            "binary_name": "linux-buildinfo-5.0.0-1012-azure",
            "binary_version": "5.0.0-1012.12~18.04.2"
          },
          {
            "binary_name": "linux-cloud-tools-5.0.0-1012-azure",
            "binary_version": "5.0.0-1012.12~18.04.2"
          },
          {
            "binary_name": "linux-headers-5.0.0-1012-azure",
            "binary_version": "5.0.0-1012.12~18.04.2"
          },
          {
            "binary_name": "linux-image-unsigned-5.0.0-1012-azure",
            "binary_version": "5.0.0-1012.12~18.04.2"
          },
          {
            "binary_name": "linux-modules-5.0.0-1012-azure",
            "binary_version": "5.0.0-1012.12~18.04.2"
          },
          {
            "binary_name": "linux-modules-extra-5.0.0-1012-azure",
            "binary_version": "5.0.0-1012.12~18.04.2"
          },
          {
            "binary_name": "linux-tools-5.0.0-1012-azure",
            "binary_version": "5.0.0-1012.12~18.04.2"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "linux-azure-edge",
        "purl": "pkg:deb/ubuntu/linux-azure-edge@5.0.0-1012.12~18.04.2?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "4.18.0-1006.6~18.04.1",
        "4.18.0-1007.7~18.04.1",
        "4.18.0-1008.8~18.04.1",
        "5.0.0-1012.12~18.04.2"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.0.0-1034-gcp",
            "binary_version": "5.0.0-1034.35"
          },
          {
            "binary_name": "linux-gcp-headers-5.0.0-1034",
            "binary_version": "5.0.0-1034.35"
          },
          {
            "binary_name": "linux-gcp-tools-5.0.0-1034",
            "binary_version": "5.0.0-1034.35"
          },
          {
            "binary_name": "linux-headers-5.0.0-1034-gcp",
            "binary_version": "5.0.0-1034.35"
          },
          {
            "binary_name": "linux-image-unsigned-5.0.0-1034-gcp",
            "binary_version": "5.0.0-1034.35"
          },
          {
            "binary_name": "linux-modules-5.0.0-1034-gcp",
            "binary_version": "5.0.0-1034.35"
          },
          {
            "binary_name": "linux-modules-extra-5.0.0-1034-gcp",
            "binary_version": "5.0.0-1034.35"
          },
          {
            "binary_name": "linux-tools-5.0.0-1034-gcp",
            "binary_version": "5.0.0-1034.35"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "linux-gcp",
        "purl": "pkg:deb/ubuntu/linux-gcp@5.0.0-1034.35?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "4.15.0-1001.1",
        "4.15.0-1003.3",
        "4.15.0-1005.5",
        "4.15.0-1006.6",
        "4.15.0-1008.8",
        "4.15.0-1009.9",
        "4.15.0-1010.10",
        "4.15.0-1014.14",
        "4.15.0-1015.15",
        "4.15.0-1017.18",
        "4.15.0-1018.19",
        "4.15.0-1019.20",
        "4.15.0-1021.22",
        "4.15.0-1023.24",
        "4.15.0-1024.25",
        "4.15.0-1025.26",
        "4.15.0-1026.27",
        "4.15.0-1027.28",
        "4.15.0-1028.29",
        "4.15.0-1029.31",
        "4.15.0-1030.32",
        "4.15.0-1032.34",
        "4.15.0-1033.35",
        "4.15.0-1034.36",
        "4.15.0-1036.38",
        "4.15.0-1037.39",
        "4.15.0-1040.42",
        "4.15.0-1042.45",
        "4.15.0-1044.70",
        "5.0.0-1020.20~18.04.1",
        "5.0.0-1021.21~18.04.1",
        "5.0.0-1025.26~18.04.1",
        "5.0.0-1026.27~18.04.1",
        "5.0.0-1028.29~18.04.1",
        "5.0.0-1029.30~18.04.1",
        "5.0.0-1031.32",
        "5.0.0-1033.34",
        "5.0.0-1034.35"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.3.0-1032-gcp",
            "binary_version": "5.3.0-1032.34~18.04.1"
          },
          {
            "binary_name": "linux-gcp-5.3-headers-5.3.0-1032",
            "binary_version": "5.3.0-1032.34~18.04.1"
          },
          {
            "binary_name": "linux-gcp-5.3-tools-5.3.0-1032",
            "binary_version": "5.3.0-1032.34~18.04.1"
          },
          {
            "binary_name": "linux-headers-5.3.0-1032-gcp",
            "binary_version": "5.3.0-1032.34~18.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.3.0-1032-gcp",
            "binary_version": "5.3.0-1032.34~18.04.1"
          },
          {
            "binary_name": "linux-modules-5.3.0-1032-gcp",
            "binary_version": "5.3.0-1032.34~18.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.3.0-1032-gcp",
            "binary_version": "5.3.0-1032.34~18.04.1"
          },
          {
            "binary_name": "linux-tools-5.3.0-1032-gcp",
            "binary_version": "5.3.0-1032.34~18.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "linux-gcp-5.3",
        "purl": "pkg:deb/ubuntu/linux-gcp-5.3@5.3.0-1032.34~18.04.1?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.3.0-1008.9~18.04.1",
        "5.3.0-1009.10~18.04.1",
        "5.3.0-1010.11~18.04.1",
        "5.3.0-1012.13~18.04.1",
        "5.3.0-1014.15~18.04.1",
        "5.3.0-1016.17~18.04.1",
        "5.3.0-1017.18~18.04.1",
        "5.3.0-1018.19~18.04.1",
        "5.3.0-1020.22~18.04.1",
        "5.3.0-1026.28~18.04.1",
        "5.3.0-1029.31~18.04.1",
        "5.3.0-1030.32~18.04.1",
        "5.3.0-1032.34~18.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-4.15.0-1079-gke",
            "binary_version": "4.15.0-1079.84"
          },
          {
            "binary_name": "linux-gke-4.15-headers-4.15.0-1079",
            "binary_version": "4.15.0-1079.84"
          },
          {
            "binary_name": "linux-gke-4.15-tools-4.15.0-1079",
            "binary_version": "4.15.0-1079.84"
          },
          {
            "binary_name": "linux-headers-4.15.0-1079-gke",
            "binary_version": "4.15.0-1079.84"
          },
          {
            "binary_name": "linux-image-unsigned-4.15.0-1079-gke",
            "binary_version": "4.15.0-1079.84"
          },
          {
            "binary_name": "linux-modules-4.15.0-1079-gke",
            "binary_version": "4.15.0-1079.84"
          },
          {
            "binary_name": "linux-modules-extra-4.15.0-1079-gke",
            "binary_version": "4.15.0-1079.84"
          },
          {
            "binary_name": "linux-tools-4.15.0-1079-gke",
            "binary_version": "4.15.0-1079.84"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "linux-gke-4.15",
        "purl": "pkg:deb/ubuntu/linux-gke-4.15@4.15.0-1079.84?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "4.15.0-1030.32",
        "4.15.0-1032.34",
        "4.15.0-1033.35",
        "4.15.0-1034.36",
        "4.15.0-1036.38",
        "4.15.0-1037.39",
        "4.15.0-1040.42",
        "4.15.0-1041.43",
        "4.15.0-1042.44",
        "4.15.0-1044.46",
        "4.15.0-1045.48",
        "4.15.0-1046.49",
        "4.15.0-1048.51",
        "4.15.0-1049.52",
        "4.15.0-1050.53",
        "4.15.0-1052.55",
        "4.15.0-1055.58",
        "4.15.0-1057.60",
        "4.15.0-1058.61",
        "4.15.0-1059.62",
        "4.15.0-1063.66",
        "4.15.0-1064.67",
        "4.15.0-1066.69",
        "4.15.0-1067.70",
        "4.15.0-1069.72",
        "4.15.0-1070.73",
        "4.15.0-1072.76",
        "4.15.0-1073.78",
        "4.15.0-1074.79",
        "4.15.0-1076.81",
        "4.15.0-1077.82",
        "4.15.0-1078.83",
        "4.15.0-1079.84"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.4.0-1080-gke",
            "binary_version": "5.4.0-1080.86~18.04.1"
          },
          {
            "binary_name": "linux-gke-5.4-headers-5.4.0-1080",
            "binary_version": "5.4.0-1080.86~18.04.1"
          },
          {
            "binary_name": "linux-gke-5.4-tools-5.4.0-1080",
            "binary_version": "5.4.0-1080.86~18.04.1"
          },
          {
            "binary_name": "linux-headers-5.4.0-1080-gke",
            "binary_version": "5.4.0-1080.86~18.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.4.0-1080-gke",
            "binary_version": "5.4.0-1080.86~18.04.1"
          },
          {
            "binary_name": "linux-modules-5.4.0-1080-gke",
            "binary_version": "5.4.0-1080.86~18.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.4.0-1080-gke",
            "binary_version": "5.4.0-1080.86~18.04.1"
          },
          {
            "binary_name": "linux-tools-5.4.0-1080-gke",
            "binary_version": "5.4.0-1080.86~18.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "linux-gke-5.4",
        "purl": "pkg:deb/ubuntu/linux-gke-5.4@5.4.0-1080.86~18.04.1?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.4.0-1025.25~18.04.1",
        "5.4.0-1027.28~18.04.1",
        "5.4.0-1029.31~18.04.1",
        "5.4.0-1030.32~18.04.1",
        "5.4.0-1032.34~18.04.1",
        "5.4.0-1033.35~18.04.1",
        "5.4.0-1035.37~18.04.1",
        "5.4.0-1036.38~18.04.1",
        "5.4.0-1037.39~18.04.1",
        "5.4.0-1039.41~18.04.1",
        "5.4.0-1040.42~18.04.1",
        "5.4.0-1042.44~18.04.1",
        "5.4.0-1043.45~18.04.1",
        "5.4.0-1044.46~18.04.1",
        "5.4.0-1046.48~18.04.1",
        "5.4.0-1049.52~18.04.1",
        "5.4.0-1051.54~18.04.1",
        "5.4.0-1052.55~18.04.1",
        "5.4.0-1053.56~18.04.1",
        "5.4.0-1054.57~18.04.1",
        "5.4.0-1055.58~18.04.1",
        "5.4.0-1056.59~18.04.1",
        "5.4.0-1057.60~18.04.1",
        "5.4.0-1059.62~18.04.1",
        "5.4.0-1061.64~18.04.1",
        "5.4.0-1062.65~18.04.1",
        "5.4.0-1063.66~18.04.1",
        "5.4.0-1065.68~18.04.1",
        "5.4.0-1066.69~18.04.1",
        "5.4.0-1067.70~18.04.1",
        "5.4.0-1068.71~18.04.1",
        "5.4.0-1071.76~18.04.3",
        "5.4.0-1072.77~18.04.1",
        "5.4.0-1074.79~18.04.1",
        "5.4.0-1076.82~18.04.1",
        "5.4.0-1078.84~18.04.1",
        "5.4.0-1080.86~18.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.4.0-1051-gkeop",
            "binary_version": "5.4.0-1051.54~18.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.4.0-1051-gkeop",
            "binary_version": "5.4.0-1051.54~18.04.1"
          },
          {
            "binary_name": "linux-gkeop-5.4-cloud-tools-5.4.0-1051",
            "binary_version": "5.4.0-1051.54~18.04.1"
          },
          {
            "binary_name": "linux-gkeop-5.4-headers-5.4.0-1051",
            "binary_version": "5.4.0-1051.54~18.04.1"
          },
          {
            "binary_name": "linux-gkeop-5.4-source-5.4.0",
            "binary_version": "5.4.0-1051.54~18.04.1"
          },
          {
            "binary_name": "linux-gkeop-5.4-tools-5.4.0-1051",
            "binary_version": "5.4.0-1051.54~18.04.1"
          },
          {
            "binary_name": "linux-headers-5.4.0-1051-gkeop",
            "binary_version": "5.4.0-1051.54~18.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.4.0-1051-gkeop",
            "binary_version": "5.4.0-1051.54~18.04.1"
          },
          {
            "binary_name": "linux-modules-5.4.0-1051-gkeop",
            "binary_version": "5.4.0-1051.54~18.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.4.0-1051-gkeop",
            "binary_version": "5.4.0-1051.54~18.04.1"
          },
          {
            "binary_name": "linux-tools-5.4.0-1051-gkeop",
            "binary_version": "5.4.0-1051.54~18.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "linux-gkeop-5.4",
        "purl": "pkg:deb/ubuntu/linux-gkeop-5.4@5.4.0-1051.54~18.04.1?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.4.0-1001.1",
        "5.4.0-1003.3",
        "5.4.0-1004.5",
        "5.4.0-1005.6",
        "5.4.0-1007.8~18.04.1",
        "5.4.0-1008.9~18.04.1",
        "5.4.0-1009.10~18.04.1",
        "5.4.0-1010.11~18.04.1",
        "5.4.0-1011.12~18.04.2",
        "5.4.0-1012.13~18.04.1",
        "5.4.0-1013.14~18.04.1",
        "5.4.0-1014.15~18.04.1",
        "5.4.0-1015.16~18.04.1",
        "5.4.0-1016.17~18.04.1",
        "5.4.0-1018.19~18.04.1",
        "5.4.0-1021.22~18.04.1",
        "5.4.0-1022.23~18.04.1",
        "5.4.0-1023.24~18.04.1",
        "5.4.0-1024.25~18.04.1",
        "5.4.0-1025.26~18.04.1",
        "5.4.0-1026.27~18.04.1",
        "5.4.0-1027.28~18.04.1",
        "5.4.0-1029.30~18.04.2",
        "5.4.0-1031.32~18.04.1",
        "5.4.0-1032.33~18.04.1",
        "5.4.0-1033.34~18.04.1",
        "5.4.0-1034.35~18.04.1",
        "5.4.0-1036.37~18.04.1",
        "5.4.0-1037.38~18.04.1",
        "5.4.0-1038.39~18.04.1",
        "5.4.0-1039.40~18.04.1",
        "5.4.0-1040.41~18.04.1",
        "5.4.0-1043.44~18.04.1",
        "5.4.0-1046.48~18.04.1",
        "5.4.0-1048.51~18.04.1",
        "5.4.0-1049.52~18.04.1",
        "5.4.0-1051.54~18.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "block-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "crypto-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "fat-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "fb-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "firewire-core-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "floppy-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "fs-core-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "fs-secondary-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "input-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "ipmi-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "kernel-image-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-buildinfo-5.3.0-76-generic",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-buildinfo-5.3.0-76-lowlatency",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-cloud-tools-5.3.0-76-generic",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-cloud-tools-5.3.0-76-lowlatency",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-headers-5.3.0-76-generic",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-headers-5.3.0-76-lowlatency",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-hwe-cloud-tools-5.3.0-76",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-hwe-headers-5.3.0-76",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-hwe-tools-5.3.0-76",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-hwe-udebs-generic",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-image-5.3.0-76-generic",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-image-5.3.0-76-lowlatency",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-image-unsigned-5.3.0-76-generic",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-image-unsigned-5.3.0-76-lowlatency",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-modules-5.3.0-76-generic",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-modules-5.3.0-76-lowlatency",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-modules-extra-5.3.0-76-generic",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-source-5.3.0",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-tools-5.3.0-76-generic",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "linux-tools-5.3.0-76-lowlatency",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "md-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "message-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "mouse-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "multipath-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "nfs-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "nic-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "nic-pcmcia-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "nic-shared-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "nic-usb-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "parport-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "pata-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "pcmcia-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "pcmcia-storage-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "plip-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "ppp-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "sata-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "scsi-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "serial-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "storage-core-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "usb-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "virtio-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          },
          {
            "binary_name": "vlan-modules-5.3.0-76-generic-di",
            "binary_version": "5.3.0-76.72"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "linux-hwe",
        "purl": "pkg:deb/ubuntu/linux-hwe@5.3.0-76.72?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "4.18.0-13.14~18.04.1",
        "4.18.0-14.15~18.04.1",
        "4.18.0-15.16~18.04.1",
        "4.18.0-16.17~18.04.1",
        "4.18.0-17.18~18.04.1",
        "4.18.0-18.19~18.04.1",
        "4.18.0-20.21~18.04.1",
        "4.18.0-21.22~18.04.1",
        "4.18.0-22.23~18.04.1",
        "4.18.0-24.25~18.04.1",
        "4.18.0-25.26~18.04.1",
        "5.0.0-23.24~18.04.1",
        "5.0.0-25.26~18.04.1",
        "5.0.0-27.28~18.04.1",
        "5.0.0-29.31~18.04.1",
        "5.0.0-31.33~18.04.1",
        "5.0.0-32.34~18.04.2",
        "5.0.0-35.38~18.04.1",
        "5.0.0-36.39~18.04.1",
        "5.0.0-37.40~18.04.1",
        "5.3.0-26.28~18.04.1",
        "5.3.0-28.30~18.04.1",
        "5.3.0-40.32~18.04.1",
        "5.3.0-42.34~18.04.1",
        "5.3.0-45.37~18.04.1",
        "5.3.0-46.38~18.04.1",
        "5.3.0-51.44~18.04.2",
        "5.3.0-53.47~18.04.1",
        "5.3.0-59.53~18.04.1",
        "5.3.0-61.55~18.04.1",
        "5.3.0-62.56~18.04.1",
        "5.3.0-64.58~18.04.1",
        "5.3.0-65.59",
        "5.3.0-66.60",
        "5.3.0-67.61",
        "5.3.0-68.63",
        "5.3.0-69.65",
        "5.3.0-70.66",
        "5.3.0-72.68",
        "5.3.0-73.69",
        "5.3.0-74.70",
        "5.3.0-75.71",
        "5.3.0-76.72"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "block-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "block-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "crypto-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "crypto-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "dasd-extra-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "dasd-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "fat-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "fat-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "fb-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "firewire-core-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "floppy-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "fs-core-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "fs-core-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "fs-secondary-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "fs-secondary-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "input-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "input-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "ipmi-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "ipmi-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "kernel-image-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "kernel-image-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-buildinfo-5.3.0-24-generic",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-buildinfo-5.3.0-24-generic-lpae",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-buildinfo-5.3.0-24-lowlatency",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-cloud-tools-5.3.0-24-generic",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-cloud-tools-5.3.0-24-lowlatency",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-headers-5.3.0-24",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-headers-5.3.0-24-generic",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-headers-5.3.0-24-generic-lpae",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-headers-5.3.0-24-lowlatency",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-hwe-edge-cloud-tools-5.3.0-24",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-hwe-edge-tools-5.3.0-24",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-hwe-edge-udebs-generic",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-hwe-edge-udebs-generic-lpae",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-image-5.3.0-24-generic",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-image-5.3.0-24-generic-lpae",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-image-5.3.0-24-lowlatency",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-image-unsigned-5.3.0-24-generic",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-image-unsigned-5.3.0-24-lowlatency",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-modules-5.3.0-24-generic",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-modules-5.3.0-24-generic-lpae",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-modules-5.3.0-24-lowlatency",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-modules-extra-5.3.0-24-generic",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-source-5.3.0",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-tools-5.3.0-24-generic",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-tools-5.3.0-24-generic-lpae",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "linux-tools-5.3.0-24-lowlatency",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "md-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "md-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "message-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "mouse-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "mouse-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "multipath-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "multipath-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "nfs-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "nfs-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "nic-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "nic-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "nic-pcmcia-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "nic-shared-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "nic-shared-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "nic-usb-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "nic-usb-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "parport-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "parport-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "pata-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "pcmcia-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "pcmcia-storage-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "plip-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "plip-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "ppp-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "ppp-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "sata-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "sata-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "scsi-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "scsi-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "serial-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "storage-core-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "storage-core-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "usb-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "usb-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "virtio-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "vlan-modules-5.3.0-24-generic-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          },
          {
            "binary_name": "vlan-modules-5.3.0-24-generic-lpae-di",
            "binary_version": "5.3.0-24.26~18.04.2"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "linux-hwe-edge",
        "purl": "pkg:deb/ubuntu/linux-hwe-edge@5.3.0-24.26~18.04.2?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.0.0-15.16~18.04.1",
        "5.0.0-16.17~18.04.1",
        "5.0.0-17.18~18.04.1",
        "5.0.0-19.20~18.04.1",
        "5.0.0-20.21~18.04.1",
        "5.3.0-19.20~18.04.2",
        "5.3.0-22.24~18.04.1",
        "5.3.0-23.25~18.04.1",
        "5.3.0-23.25~18.04.2",
        "5.3.0-24.26~18.04.2"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "block-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "crypto-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "fat-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "fb-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "firewire-core-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "floppy-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "fs-core-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "fs-secondary-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "input-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "ipmi-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "irda-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "kernel-image-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "linux-buildinfo-4.15.0-1103-oem",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "linux-headers-4.15.0-1103-oem",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "linux-image-unsigned-4.15.0-1103-oem",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "linux-modules-4.15.0-1103-oem",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "linux-oem-headers-4.15.0-1103",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "linux-oem-tools-4.15.0-1103",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "linux-tools-4.15.0-1103-oem",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "linux-udebs-oem",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "md-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "message-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "mouse-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "multipath-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "nfs-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "nic-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "nic-pcmcia-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "nic-shared-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "nic-usb-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "parport-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "pata-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "pcmcia-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "pcmcia-storage-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "plip-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "ppp-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "sata-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "scsi-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "serial-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "storage-core-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "usb-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "virtio-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          },
          {
            "binary_name": "vlan-modules-4.15.0-1103-oem-di",
            "binary_version": "4.15.0-1103.114"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "linux-oem",
        "purl": "pkg:deb/ubuntu/linux-oem@4.15.0-1103.114?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "4.15.0-1002.3",
        "4.15.0-1004.5",
        "4.15.0-1006.9",
        "4.15.0-1008.11",
        "4.15.0-1009.12",
        "4.15.0-1012.15",
        "4.15.0-1013.16",
        "4.15.0-1015.18",
        "4.15.0-1017.20",
        "4.15.0-1018.21",
        "4.15.0-1021.24",
        "4.15.0-1024.29",
        "4.15.0-1026.31",
        "4.15.0-1028.33",
        "4.15.0-1030.35",
        "4.15.0-1033.38",
        "4.15.0-1034.39",
        "4.15.0-1035.40",
        "4.15.0-1036.41",
        "4.15.0-1038.43",
        "4.15.0-1039.44",
        "4.15.0-1043.48",
        "4.15.0-1045.50",
        "4.15.0-1050.57",
        "4.15.0-1056.65",
        "4.15.0-1057.66",
        "4.15.0-1059.68",
        "4.15.0-1063.72",
        "4.15.0-1064.73",
        "4.15.0-1065.75",
        "4.15.0-1066.76",
        "4.15.0-1067.77",
        "4.15.0-1069.79",
        "4.15.0-1073.83",
        "4.15.0-1076.86",
        "4.15.0-1079.89",
        "4.15.0-1080.90",
        "4.15.0-1081.91",
        "4.15.0-1087.97",
        "4.15.0-1090.100",
        "4.15.0-1091.101",
        "4.15.0-1093.103",
        "4.15.0-1094.104",
        "4.15.0-1096.106",
        "4.15.0-1097.107",
        "4.15.0-1099.109",
        "4.15.0-1100.110",
        "4.15.0-1101.112",
        "4.15.0-1102.113",
        "4.15.0-1103.114"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.0.0-1014-oracle",
            "binary_version": "5.0.0-1014.19"
          },
          {
            "binary_name": "linux-headers-5.0.0-1014-oracle",
            "binary_version": "5.0.0-1014.19"
          },
          {
            "binary_name": "linux-image-unsigned-5.0.0-1014-oracle",
            "binary_version": "5.0.0-1014.19"
          },
          {
            "binary_name": "linux-modules-5.0.0-1014-oracle",
            "binary_version": "5.0.0-1014.19"
          },
          {
            "binary_name": "linux-modules-extra-5.0.0-1014-oracle",
            "binary_version": "5.0.0-1014.19"
          },
          {
            "binary_name": "linux-oracle-5.0-headers-5.0.0-1014",
            "binary_version": "5.0.0-1014.19"
          },
          {
            "binary_name": "linux-oracle-5.0-tools-5.0.0-1014",
            "binary_version": "5.0.0-1014.19"
          },
          {
            "binary_name": "linux-tools-5.0.0-1014-oracle",
            "binary_version": "5.0.0-1014.19"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "linux-oracle-5.0",
        "purl": "pkg:deb/ubuntu/linux-oracle-5.0@5.0.0-1014.19?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.0.0-1007.12~18.04.1",
        "5.0.0-1008.13~18.04.1",
        "5.0.0-1009.14~18.04.1",
        "5.0.0-1010.15~18.04.1",
        "5.0.0-1011.16",
        "5.0.0-1013.18",
        "5.0.0-1014.19"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.3.0-1030-oracle",
            "binary_version": "5.3.0-1030.32~18.04.1"
          },
          {
            "binary_name": "linux-headers-5.3.0-1030-oracle",
            "binary_version": "5.3.0-1030.32~18.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.3.0-1030-oracle",
            "binary_version": "5.3.0-1030.32~18.04.1"
          },
          {
            "binary_name": "linux-modules-5.3.0-1030-oracle",
            "binary_version": "5.3.0-1030.32~18.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.3.0-1030-oracle",
            "binary_version": "5.3.0-1030.32~18.04.1"
          },
          {
            "binary_name": "linux-oracle-5.3-headers-5.3.0-1030",
            "binary_version": "5.3.0-1030.32~18.04.1"
          },
          {
            "binary_name": "linux-oracle-5.3-tools-5.3.0-1030",
            "binary_version": "5.3.0-1030.32~18.04.1"
          },
          {
            "binary_name": "linux-tools-5.3.0-1030-oracle",
            "binary_version": "5.3.0-1030.32~18.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "linux-oracle-5.3",
        "purl": "pkg:deb/ubuntu/linux-oracle-5.3@5.3.0-1030.32~18.04.1?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.3.0-1011.12~18.04.1",
        "5.3.0-1013.14~18.04.1",
        "5.3.0-1014.15~18.04.1",
        "5.3.0-1016.18~18.04.1",
        "5.3.0-1018.20~18.04.1",
        "5.3.0-1024.26~18.04.1",
        "5.3.0-1027.29~18.04.1",
        "5.3.0-1028.30~18.04.1",
        "5.3.0-1030.32~18.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-aws-5.15-cloud-tools-5.15.0-1073",
            "binary_version": "5.15.0-1073.79~20.04.1"
          },
          {
            "binary_name": "linux-aws-5.15-headers-5.15.0-1073",
            "binary_version": "5.15.0-1073.79~20.04.1"
          },
          {
            "binary_name": "linux-aws-5.15-tools-5.15.0-1073",
            "binary_version": "5.15.0-1073.79~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-1073-aws",
            "binary_version": "5.15.0-1073.79~20.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-1073-aws",
            "binary_version": "5.15.0-1073.79~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.15.0-1073-aws",
            "binary_version": "5.15.0-1073.79~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1073-aws",
            "binary_version": "5.15.0-1073.79~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.15.0-1073-aws",
            "binary_version": "5.15.0-1073.79~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1073-aws",
            "binary_version": "5.15.0-1073.79~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.15.0-1073-aws",
            "binary_version": "5.15.0-1073.79~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-aws-5.15",
        "purl": "pkg:deb/ubuntu/linux-aws-5.15@5.15.0-1073.79~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1073.79~20.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1014.18~20.04.1",
        "5.15.0-1015.19~20.04.1",
        "5.15.0-1017.21~20.04.1",
        "5.15.0-1019.23~20.04.1",
        "5.15.0-1020.24~20.04.1",
        "5.15.0-1021.25~20.04.1",
        "5.15.0-1022.26~20.04.1",
        "5.15.0-1023.27~20.04.1",
        "5.15.0-1026.30~20.04.2",
        "5.15.0-1027.31~20.04.1",
        "5.15.0-1028.32~20.04.1",
        "5.15.0-1030.34~20.04.1",
        "5.15.0-1031.35~20.04.1",
        "5.15.0-1033.37~20.04.1",
        "5.15.0-1034.38~20.04.1",
        "5.15.0-1035.39~20.04.1",
        "5.15.0-1036.40~20.04.1",
        "5.15.0-1037.41~20.04.1",
        "5.15.0-1038.43~20.04.1",
        "5.15.0-1039.44~20.04.1",
        "5.15.0-1040.45~20.04.1",
        "5.15.0-1041.46~20.04.1",
        "5.15.0-1043.48~20.04.1",
        "5.15.0-1044.49~20.04.1",
        "5.15.0-1045.50~20.04.1",
        "5.15.0-1047.52~20.04.1",
        "5.15.0-1048.53~20.04.1",
        "5.15.0-1049.54~20.04.1",
        "5.15.0-1050.55~20.04.1",
        "5.15.0-1051.56~20.04.1",
        "5.15.0-1052.57~20.04.1",
        "5.15.0-1053.58~20.04.1",
        "5.15.0-1055.60~20.04.1",
        "5.15.0-1056.61~20.04.1",
        "5.15.0-1057.63~20.04.1",
        "5.15.0-1058.64~20.04.1",
        "5.15.0-1061.67~20.04.1",
        "5.15.0-1062.68~20.04.1",
        "5.15.0-1063.69~20.04.1",
        "5.15.0-1064.70~20.04.1",
        "5.15.0-1065.71~20.04.1",
        "5.15.0-1066.72~20.04.1",
        "5.15.0-1067.73~20.04.1",
        "5.15.0-1068.74~20.04.1",
        "5.15.0-1069.75~20.04.1",
        "5.15.0-1070.76~20.04.1",
        "5.15.0-1071.77~20.04.1",
        "5.15.0-1072.78~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-azure-5.15-cloud-tools-5.15.0-1078",
            "binary_version": "5.15.0-1078.87~20.04.1"
          },
          {
            "binary_name": "linux-azure-5.15-headers-5.15.0-1078",
            "binary_version": "5.15.0-1078.87~20.04.1"
          },
          {
            "binary_name": "linux-azure-5.15-tools-5.15.0-1078",
            "binary_version": "5.15.0-1078.87~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-1078-azure",
            "binary_version": "5.15.0-1078.87~20.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-1078-azure",
            "binary_version": "5.15.0-1078.87~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.15.0-1078-azure",
            "binary_version": "5.15.0-1078.87~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1078-azure",
            "binary_version": "5.15.0-1078.87~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.15.0-1078-azure",
            "binary_version": "5.15.0-1078.87~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1078-azure",
            "binary_version": "5.15.0-1078.87~20.04.1"
          },
          {
            "binary_name": "linux-modules-involflt-5.15.0-1078-azure",
            "binary_version": "5.15.0-1078.87~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.15.0-1078-azure",
            "binary_version": "5.15.0-1078.87~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-azure-5.15",
        "purl": "pkg:deb/ubuntu/linux-azure-5.15@5.15.0-1078.87~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1078.87~20.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1007.8~20.04.1",
        "5.15.0-1008.9~20.04.1",
        "5.15.0-1013.16~20.04.1",
        "5.15.0-1014.17~20.04.1",
        "5.15.0-1017.20~20.04.1",
        "5.15.0-1019.24~20.04.1",
        "5.15.0-1020.25~20.04.1",
        "5.15.0-1021.26~20.04.1",
        "5.15.0-1022.27~20.04.1",
        "5.15.0-1023.29~20.04.1",
        "5.15.0-1029.36~20.04.1",
        "5.15.0-1030.37~20.04.1",
        "5.15.0-1031.38~20.04.1",
        "5.15.0-1033.40~20.04.1",
        "5.15.0-1034.41~20.04.1",
        "5.15.0-1035.42~20.04.1",
        "5.15.0-1036.43~20.04.1",
        "5.15.0-1037.44~20.04.1",
        "5.15.0-1038.45~20.04.1",
        "5.15.0-1039.46~20.04.1",
        "5.15.0-1040.47~20.04.1",
        "5.15.0-1041.48~20.04.1",
        "5.15.0-1042.49~20.04.1",
        "5.15.0-1043.50~20.04.1",
        "5.15.0-1045.52~20.04.1",
        "5.15.0-1046.53~20.04.1",
        "5.15.0-1047.54~20.04.1",
        "5.15.0-1049.56~20.04.1",
        "5.15.0-1050.57~20.04.1",
        "5.15.0-1051.59~20.04.1",
        "5.15.0-1052.60~20.04.1",
        "5.15.0-1053.61~20.04.1",
        "5.15.0-1054.62~20.04.1",
        "5.15.0-1056.64~20.04.1",
        "5.15.0-1057.65~20.04.1",
        "5.15.0-1058.66~20.04.2",
        "5.15.0-1059.67~20.04.1",
        "5.15.0-1060.69~20.04.1",
        "5.15.0-1061.70~20.04.1",
        "5.15.0-1063.72~20.04.1",
        "5.15.0-1064.73~20.04.1",
        "5.15.0-1065.74~20.04.1",
        "5.15.0-1067.76~20.04.1",
        "5.15.0-1068.77~20.04.1",
        "5.15.0-1070.79~20.04.1",
        "5.15.0-1071.80~20.04.1",
        "5.15.0-1072.81~20.04.1",
        "5.15.0-1073.82~20.04.1",
        "5.15.0-1074.83~20.04.1",
        "5.15.0-1075.84~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1072-gcp",
            "binary_version": "5.15.0-1072.80~20.04.1"
          },
          {
            "binary_name": "linux-gcp-5.15-headers-5.15.0-1072",
            "binary_version": "5.15.0-1072.80~20.04.1"
          },
          {
            "binary_name": "linux-gcp-5.15-tools-5.15.0-1072",
            "binary_version": "5.15.0-1072.80~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.15.0-1072-gcp",
            "binary_version": "5.15.0-1072.80~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1072-gcp",
            "binary_version": "5.15.0-1072.80~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.15.0-1072-gcp",
            "binary_version": "5.15.0-1072.80~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1072-gcp",
            "binary_version": "5.15.0-1072.80~20.04.1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-5.15.0-1072-gcp",
            "binary_version": "5.15.0-1072.80~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.15.0-1072-gcp",
            "binary_version": "5.15.0-1072.80~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-gcp-5.15",
        "purl": "pkg:deb/ubuntu/linux-gcp-5.15@5.15.0-1072.80~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1072.80~20.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1006.9~20.04.1",
        "5.15.0-1012.17~20.04.1",
        "5.15.0-1013.18~20.04.1",
        "5.15.0-1016.21~20.04.1",
        "5.15.0-1017.23~20.04.2",
        "5.15.0-1018.24~20.04.1",
        "5.15.0-1021.28~20.04.1",
        "5.15.0-1022.29~20.04.1",
        "5.15.0-1025.32~20.04.2",
        "5.15.0-1026.33~20.04.1",
        "5.15.0-1027.34~20.04.1",
        "5.15.0-1029.36~20.04.1",
        "5.15.0-1030.37~20.04.1",
        "5.15.0-1031.38~20.04.1",
        "5.15.0-1032.40~20.04.1",
        "5.15.0-1033.41~20.04.1",
        "5.15.0-1034.42~20.04.1",
        "5.15.0-1035.43~20.04.1",
        "5.15.0-1036.44~20.04.1",
        "5.15.0-1037.45~20.04.1",
        "5.15.0-1038.46~20.04.1",
        "5.15.0-1039.47~20.04.1",
        "5.15.0-1040.48~20.04.1",
        "5.15.0-1041.49~20.04.1",
        "5.15.0-1042.50~20.04.1",
        "5.15.0-1044.52~20.04.1",
        "5.15.0-1045.53~20.04.2",
        "5.15.0-1046.54~20.04.1",
        "5.15.0-1047.55~20.04.1",
        "5.15.0-1048.56~20.04.1",
        "5.15.0-1049.57~20.04.1",
        "5.15.0-1051.59~20.04.1",
        "5.15.0-1052.60~20.04.1",
        "5.15.0-1053.61~20.04.1",
        "5.15.0-1054.62~20.04.1",
        "5.15.0-1055.63~20.04.1",
        "5.15.0-1058.66~20.04.1",
        "5.15.0-1059.67~20.04.1",
        "5.15.0-1060.68~20.04.1",
        "5.15.0-1062.70~20.04.1",
        "5.15.0-1065.73~20.04.1",
        "5.15.0-1066.74~20.04.1",
        "5.15.0-1067.75~20.04.1",
        "5.15.0-1068.76~20.04.1",
        "5.15.0-1069.77~20.04.1",
        "5.15.0-1070.78~20.04.1",
        "5.15.0-1071.79~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-127-generic",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-127-generic-64k",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-127-generic-lpae",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-127-generic",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.15.0-127-generic",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.15.0-127-generic-64k",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.15.0-127-generic-lpae",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.15-cloud-tools-5.15.0-127",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.15-headers-5.15.0-127",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.15-tools-5.15.0-127",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-image-5.15.0-127-generic",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-image-5.15.0-127-generic-lpae",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-127-generic",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-127-generic-64k",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.15.0-127-generic",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.15.0-127-generic-64k",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.15.0-127-generic-lpae",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-127-generic",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-5.15.0-127-generic",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.15.0-127-generic",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.15.0-127-generic-64k",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.15.0-127-generic-lpae",
            "binary_version": "5.15.0-127.137~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-hwe-5.15",
        "purl": "pkg:deb/ubuntu/linux-hwe-5.15@5.15.0-127.137~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-127.137~20.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-33.34~20.04.1",
        "5.15.0-41.44~20.04.1",
        "5.15.0-43.46~20.04.1",
        "5.15.0-46.49~20.04.1",
        "5.15.0-48.54~20.04.1",
        "5.15.0-50.56~20.04.1",
        "5.15.0-52.58~20.04.1",
        "5.15.0-53.59~20.04.1",
        "5.15.0-56.62~20.04.1",
        "5.15.0-57.63~20.04.1",
        "5.15.0-58.64~20.04.1",
        "5.15.0-60.66~20.04.1",
        "5.15.0-67.74~20.04.1",
        "5.15.0-69.76~20.04.1",
        "5.15.0-70.77~20.04.1",
        "5.15.0-71.78~20.04.1",
        "5.15.0-72.79~20.04.1",
        "5.15.0-73.80~20.04.1",
        "5.15.0-75.82~20.04.1",
        "5.15.0-76.83~20.04.1",
        "5.15.0-78.85~20.04.1",
        "5.15.0-79.86~20.04.2",
        "5.15.0-82.91~20.04.1",
        "5.15.0-83.92~20.04.1",
        "5.15.0-84.93~20.04.1",
        "5.15.0-86.96~20.04.1",
        "5.15.0-87.97~20.04.1",
        "5.15.0-88.98~20.04.1",
        "5.15.0-89.99~20.04.1",
        "5.15.0-91.101~20.04.1",
        "5.15.0-92.102~20.04.1",
        "5.15.0-94.104~20.04.1",
        "5.15.0-97.107~20.04.1",
        "5.15.0-100.110~20.04.1",
        "5.15.0-101.111~20.04.1",
        "5.15.0-102.112~20.04.1",
        "5.15.0-105.115~20.04.1",
        "5.15.0-106.116~20.04.1",
        "5.15.0-107.117~20.04.1",
        "5.15.0-113.123~20.04.1",
        "5.15.0-116.126~20.04.1",
        "5.15.0-117.127~20.04.1",
        "5.15.0-118.128~20.04.1",
        "5.15.0-119.129~20.04.1",
        "5.15.0-121.131~20.04.1",
        "5.15.0-122.132~20.04.1",
        "5.15.0-124.134~20.04.1",
        "5.15.0-125.135~20.04.1",
        "5.15.0-126.136~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1066-ibm",
            "binary_version": "5.15.0-1066.69~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.15.0-1066-ibm",
            "binary_version": "5.15.0-1066.69~20.04.1"
          },
          {
            "binary_name": "linux-ibm-5.15-headers-5.15.0-1066",
            "binary_version": "5.15.0-1066.69~20.04.1"
          },
          {
            "binary_name": "linux-ibm-5.15-source-5.15.0",
            "binary_version": "5.15.0-1066.69~20.04.1"
          },
          {
            "binary_name": "linux-ibm-5.15-tools-5.15.0-1066",
            "binary_version": "5.15.0-1066.69~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1066-ibm",
            "binary_version": "5.15.0-1066.69~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.15.0-1066-ibm",
            "binary_version": "5.15.0-1066.69~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1066-ibm",
            "binary_version": "5.15.0-1066.69~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.15.0-1066-ibm",
            "binary_version": "5.15.0-1066.69~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-ibm-5.15",
        "purl": "pkg:deb/ubuntu/linux-ibm-5.15@5.15.0-1066.69~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1066.69~20.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1033.36~20.04.1",
        "5.15.0-1034.37~20.04.1",
        "5.15.0-1035.38~20.04.1",
        "5.15.0-1036.39~20.04.1",
        "5.15.0-1037.40~20.04.1",
        "5.15.0-1038.41~20.04.1",
        "5.15.0-1040.43~20.04.1",
        "5.15.0-1041.44~20.04.1",
        "5.15.0-1042.45~20.04.1",
        "5.15.0-1043.46~20.04.1",
        "5.15.0-1044.47~20.04.1",
        "5.15.0-1045.48~20.04.1",
        "5.15.0-1046.49~20.04.1",
        "5.15.0-1047.50~20.04.1",
        "5.15.0-1048.51~20.04.1",
        "5.15.0-1049.52~20.04.1",
        "5.15.0-1050.53~20.04.1",
        "5.15.0-1053.56~20.04.1",
        "5.15.0-1054.57~20.04.1",
        "5.15.0-1055.58~20.04.1",
        "5.15.0-1057.60~20.04.1",
        "5.15.0-1058.61~20.04.1",
        "5.15.0-1059.62~20.04.1",
        "5.15.0-1060.63~20.04.1",
        "5.15.0-1061.64~20.04.1",
        "5.15.0-1062.65~20.04.1",
        "5.15.0-1063.66~20.04.1",
        "5.15.0-1064.67~20.04.1",
        "5.15.0-1065.68~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1071-intel-iotg",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-1071-intel-iotg",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.15.0-1071-intel-iotg",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1071-intel-iotg",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-intel-iotg-5.15-cloud-tools-5.15.0-1071",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-intel-iotg-5.15-cloud-tools-common",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-intel-iotg-5.15-headers-5.15.0-1071",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-intel-iotg-5.15-tools-5.15.0-1071",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-intel-iotg-5.15-tools-common",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-intel-iotg-5.15-tools-host",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.15.0-1071-intel-iotg",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1071-intel-iotg",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-5.15.0-1071-intel-iotg",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.15.0-1071-intel-iotg",
            "binary_version": "5.15.0-1071.77~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-intel-iotg-5.15",
        "purl": "pkg:deb/ubuntu/linux-intel-iotg-5.15@5.15.0-1071.77~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1071.77~20.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1003.5~20.04.1",
        "5.15.0-1008.11~20.04.1",
        "5.15.0-1010.14~20.04.1",
        "5.15.0-1015.20~20.04.2",
        "5.15.0-1016.21~20.04.1",
        "5.15.0-1017.22~20.04.1",
        "5.15.0-1018.23~20.04.1",
        "5.15.0-1021.26~20.04.1",
        "5.15.0-1023.28~20.04.1",
        "5.15.0-1025.30~20.04.1",
        "5.15.0-1026.31~20.04.1",
        "5.15.0-1027.32~20.04.1",
        "5.15.0-1030.35~20.04.1",
        "5.15.0-1031.36~20.04.1",
        "5.15.0-1033.38~20.04.1",
        "5.15.0-1034.39~20.04.1",
        "5.15.0-1036.41~20.04.1",
        "5.15.0-1037.42~20.04.1",
        "5.15.0-1038.43~20.04.1",
        "5.15.0-1040.46~20.04.1",
        "5.15.0-1043.49~20.04.1",
        "5.15.0-1045.51~20.04.1",
        "5.15.0-1046.52~20.04.1",
        "5.15.0-1048.54~20.04.1",
        "5.15.0-1049.55~20.04.1",
        "5.15.0-1050.56~20.04.1",
        "5.15.0-1051.57~20.04.1",
        "5.15.0-1052.58~20.04.1",
        "5.15.0-1055.61~20.04.1",
        "5.15.0-1058.64~20.04.1",
        "5.15.0-1059.65~20.04.1",
        "5.15.0-1060.66~20.04.1",
        "5.15.0-1061.67~20.04.1",
        "5.15.0-1062.68~20.04.1",
        "5.15.0-1063.69~20.04.1",
        "5.15.0-1064.70~20.04.1",
        "5.15.0-1065.71~20.04.1",
        "5.15.0-1066.72~20.04.1",
        "5.15.0-1067.73~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-127-lowlatency",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-127-lowlatency-64k",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-127-lowlatency",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.15.0-127-lowlatency",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.15.0-127-lowlatency-64k",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-127-lowlatency",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-127-lowlatency-64k",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-5.15-cloud-tools-5.15.0-127",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-5.15-headers-5.15.0-127",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-5.15-tools-5.15.0-127",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.15.0-127-lowlatency",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.15.0-127-lowlatency-64k",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-5.15.0-127-lowlatency",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.15.0-127-lowlatency",
            "binary_version": "5.15.0-127.137~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.15.0-127-lowlatency-64k",
            "binary_version": "5.15.0-127.137~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-lowlatency-hwe-5.15",
        "purl": "pkg:deb/ubuntu/linux-lowlatency-hwe-5.15@5.15.0-127.137~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-127.137~20.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-33.34~20.04.1",
        "5.15.0-42.45~20.04.1",
        "5.15.0-43.46~20.04.1",
        "5.15.0-46.49~20.04.1",
        "5.15.0-48.54~20.04.1",
        "5.15.0-50.56~20.04.1",
        "5.15.0-52.58~20.04.1",
        "5.15.0-53.59~20.04.1",
        "5.15.0-56.62~20.04.1",
        "5.15.0-58.64~20.04.1",
        "5.15.0-60.66~20.04.1",
        "5.15.0-67.74~20.04.1",
        "5.15.0-69.76~20.04.1",
        "5.15.0-70.77~20.04.1",
        "5.15.0-71.78~20.04.1",
        "5.15.0-72.79~20.04.1",
        "5.15.0-73.80~20.04.1",
        "5.15.0-75.82~20.04.1",
        "5.15.0-76.83~20.04.1",
        "5.15.0-78.85~20.04.1",
        "5.15.0-79.88~20.04.1",
        "5.15.0-82.91~20.04.1",
        "5.15.0-83.92~20.04.1",
        "5.15.0-84.93~20.04.1",
        "5.15.0-86.95~20.04.1",
        "5.15.0-87.96~20.04.1",
        "5.15.0-88.98~20.04.1",
        "5.15.0-89.99~20.04.1",
        "5.15.0-91.101~20.04.1",
        "5.15.0-92.102~20.04.1",
        "5.15.0-94.104~20.04.1",
        "5.15.0-97.107~20.04.1",
        "5.15.0-100.110~20.04.1",
        "5.15.0-101.111~20.04.1",
        "5.15.0-102.112~20.04.1",
        "5.15.0-105.115~20.04.1",
        "5.15.0-106.116~20.04.1",
        "5.15.0-107.117~20.04.1",
        "5.15.0-110.120~20.04.1",
        "5.15.0-113.123~20.04.1",
        "5.15.0-116.126~20.04.1",
        "5.15.0-117.127~20.04.1",
        "5.15.0-118.128~20.04.1",
        "5.15.0-119.129~20.04.1",
        "5.15.0-121.131~20.04.1",
        "5.15.0-122.132~20.04.1",
        "5.15.0-124.134~20.04.1",
        "5.15.0-125.135~20.04.1",
        "5.15.0-126.136~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1032-nvidia-tegra",
            "binary_version": "5.15.0-1032.32~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-1032-nvidia-tegra-rt",
            "binary_version": "5.15.0-1032.32~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.15.0-1032-nvidia-tegra",
            "binary_version": "5.15.0-1032.32~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.15.0-1032-nvidia-tegra-rt",
            "binary_version": "5.15.0-1032.32~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1032-nvidia-tegra",
            "binary_version": "5.15.0-1032.32~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1032-nvidia-tegra-rt",
            "binary_version": "5.15.0-1032.32~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.15.0-1032-nvidia-tegra",
            "binary_version": "5.15.0-1032.32~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.15.0-1032-nvidia-tegra-rt",
            "binary_version": "5.15.0-1032.32~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1032-nvidia-tegra",
            "binary_version": "5.15.0-1032.32~20.04.1"
          },
          {
            "binary_name": "linux-nvidia-tegra-5.15-headers-5.15.0-1032",
            "binary_version": "5.15.0-1032.32~20.04.1"
          },
          {
            "binary_name": "linux-nvidia-tegra-5.15-tools-5.15.0-1032",
            "binary_version": "5.15.0-1032.32~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.15.0-1032-nvidia-tegra",
            "binary_version": "5.15.0-1032.32~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.15.0-1032-nvidia-tegra-rt",
            "binary_version": "5.15.0-1032.32~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-nvidia-tegra-5.15",
        "purl": "pkg:deb/ubuntu/linux-nvidia-tegra-5.15@5.15.0-1032.32~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1032.32~20.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1009.9~20.04.1",
        "5.15.0-1010.10~20.04.1",
        "5.15.0-1012.12~20.04.1",
        "5.15.0-1014.14~20.04.1",
        "5.15.0-1015.15~20.04.1",
        "5.15.0-1016.16~20.04.1",
        "5.15.0-1017.17~20.04.1",
        "5.15.0-1018.18~20.04.1",
        "5.15.0-1019.19~20.04.1",
        "5.15.0-1020.20~20.04.1",
        "5.15.0-1022.22~20.04.1",
        "5.15.0-1025.25~20.04.1",
        "5.15.0-1027.27~20.04.1",
        "5.15.0-1030.30~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1071-oracle",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.15.0-1071-oracle",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1071-oracle",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.15.0-1071-oracle",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1071-oracle",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-oracle-5.15-headers-5.15.0-1071",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-oracle-5.15-tools-5.15.0-1071",
            "binary_version": "5.15.0-1071.77~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.15.0-1071-oracle",
            "binary_version": "5.15.0-1071.77~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-oracle-5.15",
        "purl": "pkg:deb/ubuntu/linux-oracle-5.15@5.15.0-1071.77~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1071.77~20.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1007.9~20.04.1",
        "5.15.0-1013.17~20.04.1",
        "5.15.0-1016.20~20.04.1",
        "5.15.0-1017.22~20.04.1",
        "5.15.0-1018.23~20.04.1",
        "5.15.0-1019.24~20.04.1",
        "5.15.0-1021.27~20.04.1",
        "5.15.0-1022.28~20.04.1",
        "5.15.0-1025.31~20.04.2",
        "5.15.0-1027.33~20.04.1",
        "5.15.0-1029.35~20.04.1",
        "5.15.0-1030.36~20.04.1",
        "5.15.0-1032.38~20.04.1",
        "5.15.0-1033.39~20.04.1",
        "5.15.0-1034.40~20.04.1",
        "5.15.0-1035.41~20.04.1",
        "5.15.0-1036.42~20.04.1",
        "5.15.0-1037.43~20.04.1",
        "5.15.0-1038.44~20.04.1",
        "5.15.0-1039.45~20.04.1",
        "5.15.0-1040.46~20.04.1",
        "5.15.0-1041.47~20.04.1",
        "5.15.0-1042.48~20.04.1",
        "5.15.0-1044.50~20.04.1",
        "5.15.0-1045.51~20.04.1",
        "5.15.0-1046.52~20.04.1",
        "5.15.0-1047.53~20.04.1",
        "5.15.0-1048.54~20.04.1",
        "5.15.0-1049.55~20.04.1",
        "5.15.0-1050.56~20.04.1",
        "5.15.0-1051.57~20.04.1",
        "5.15.0-1052.58~20.04.1",
        "5.15.0-1053.59~20.04.1",
        "5.15.0-1054.60~20.04.1",
        "5.15.0-1055.61~20.04.1",
        "5.15.0-1058.64~20.04.1",
        "5.15.0-1059.65~20.04.1",
        "5.15.0-1061.67~20.04.1",
        "5.15.0-1062.68~20.04.1",
        "5.15.0-1063.69~20.04.1",
        "5.15.0-1065.71~20.04.1",
        "5.15.0-1066.72~20.04.1",
        "5.15.0-1067.73~20.04.1",
        "5.15.0-1068.74~20.04.1",
        "5.15.0-1069.75~20.04.1",
        "5.15.0-1070.76~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1069-generic",
            "binary_version": "5.15.0-1069.73~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.15.0-1069-generic",
            "binary_version": "5.15.0-1069.73~20.04.1"
          },
          {
            "binary_name": "linux-image-5.15.0-1069-generic",
            "binary_version": "5.15.0-1069.73~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.15.0-1069-generic",
            "binary_version": "5.15.0-1069.73~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1069-generic",
            "binary_version": "5.15.0-1069.73~20.04.1"
          },
          {
            "binary_name": "linux-riscv-5.15-headers-5.15.0-1069",
            "binary_version": "5.15.0-1069.73~20.04.1"
          },
          {
            "binary_name": "linux-riscv-5.15-tools-5.15.0-1069",
            "binary_version": "5.15.0-1069.73~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.15.0-1069-generic",
            "binary_version": "5.15.0-1069.73~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-riscv-5.15",
        "purl": "pkg:deb/ubuntu/linux-riscv-5.15@5.15.0-1069.73~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1069.73~20.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1015.17~20.04.1",
        "5.15.0-1017.19~20.04.1",
        "5.15.0-1018.21~20.04.1",
        "5.15.0-1019.22~20.04.1",
        "5.15.0-1022.26~20.04.1",
        "5.15.0-1023.27~20.04.1",
        "5.15.0-1026.30~20.04.2",
        "5.15.0-1027.31~20.04.1",
        "5.15.0-1028.32~20.04.1",
        "5.15.0-1029.33~20.04.1",
        "5.15.0-1030.34~20.04.1",
        "5.15.0-1031.35~20.04.1",
        "5.15.0-1032.36~20.04.1",
        "5.15.0-1033.37~20.04.1",
        "5.15.0-1034.38~20.04.1",
        "5.15.0-1035.39~20.04.1",
        "5.15.0-1036.40~20.04.2",
        "5.15.0-1037.41~20.04.2",
        "5.15.0-1038.42~20.04.2",
        "5.15.0-1039.43~20.04.2",
        "5.15.0-1040.44~20.04.3",
        "5.15.0-1041.45~20.04.1",
        "5.15.0-1043.47~20.04.1",
        "5.15.0-1044.48~20.04.1",
        "5.15.0-1045.49~20.04.1",
        "5.15.0-1046.50~20.04.1",
        "5.15.0-1047.51~20.04.1",
        "5.15.0-1048.52~20.04.1",
        "5.15.0-1049.53~20.04.2",
        "5.15.0-1050.54~20.04.1",
        "5.15.0-1051.55~20.04.1",
        "5.15.0-1052.56~20.04.1",
        "5.15.0-1053.57~20.04.1",
        "5.15.0-1056.60~20.04.1",
        "5.15.0-1057.61~20.04.1",
        "5.15.0-1058.62~20.04.1",
        "5.15.0-1059.63~20.04.1",
        "5.15.0-1060.64~20.04.1",
        "5.15.0-1061.65~20.04.1",
        "5.15.0-1062.66~20.04.1",
        "5.15.0-1063.67~20.04.1",
        "5.15.0-1064.68~20.04.1",
        "5.15.0-1065.69~20.04.1",
        "5.15.0-1066.70~20.04.1",
        "5.15.0-1067.71~20.04.1",
        "5.15.0-1068.72~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-aws-5.11-cloud-tools-5.11.0-1028",
            "binary_version": "5.11.0-1028.31~20.04.1"
          },
          {
            "binary_name": "linux-aws-5.11-headers-5.11.0-1028",
            "binary_version": "5.11.0-1028.31~20.04.1"
          },
          {
            "binary_name": "linux-aws-5.11-tools-5.11.0-1028",
            "binary_version": "5.11.0-1028.31~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.11.0-1028-aws",
            "binary_version": "5.11.0-1028.31~20.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.11.0-1028-aws",
            "binary_version": "5.11.0-1028.31~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.11.0-1028-aws",
            "binary_version": "5.11.0-1028.31~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.11.0-1028-aws",
            "binary_version": "5.11.0-1028.31~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.11.0-1028-aws",
            "binary_version": "5.11.0-1028.31~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.11.0-1028-aws",
            "binary_version": "5.11.0-1028.31~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.11.0-1028-aws",
            "binary_version": "5.11.0-1028.31~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-aws-5.11",
        "purl": "pkg:deb/ubuntu/linux-aws-5.11@5.11.0-1028.31~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.11.0-1009.9~20.04.2",
        "5.11.0-1014.15~20.04.1",
        "5.11.0-1016.17~20.04.1",
        "5.11.0-1017.18~20.04.1",
        "5.11.0-1019.20~20.04.1",
        "5.11.0-1020.21~20.04.2",
        "5.11.0-1021.22~20.04.2",
        "5.11.0-1022.23~20.04.1",
        "5.11.0-1023.24~20.04.1",
        "5.11.0-1025.27~20.04.1",
        "5.11.0-1027.30~20.04.1",
        "5.11.0-1028.31~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-aws-5.13-cloud-tools-5.13.0-1031",
            "binary_version": "5.13.0-1031.35~20.04.1"
          },
          {
            "binary_name": "linux-aws-5.13-headers-5.13.0-1031",
            "binary_version": "5.13.0-1031.35~20.04.1"
          },
          {
            "binary_name": "linux-aws-5.13-tools-5.13.0-1031",
            "binary_version": "5.13.0-1031.35~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.13.0-1031-aws",
            "binary_version": "5.13.0-1031.35~20.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.13.0-1031-aws",
            "binary_version": "5.13.0-1031.35~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.13.0-1031-aws",
            "binary_version": "5.13.0-1031.35~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.13.0-1031-aws",
            "binary_version": "5.13.0-1031.35~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.13.0-1031-aws",
            "binary_version": "5.13.0-1031.35~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.13.0-1031-aws",
            "binary_version": "5.13.0-1031.35~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.13.0-1031-aws",
            "binary_version": "5.13.0-1031.35~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-aws-5.13",
        "purl": "pkg:deb/ubuntu/linux-aws-5.13@5.13.0-1031.35~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.13.0-1008.9~20.04.2",
        "5.13.0-1011.12~20.04.1",
        "5.13.0-1012.13~20.04.1",
        "5.13.0-1014.15~20.04.1",
        "5.13.0-1017.19~20.04.1",
        "5.13.0-1019.21~20.04.1",
        "5.13.0-1021.23~20.04.2",
        "5.13.0-1022.24~20.04.1",
        "5.13.0-1023.25~20.04.1",
        "5.13.0-1025.27~20.04.1",
        "5.13.0-1028.31~20.04.1",
        "5.13.0-1029.32~20.04.1",
        "5.13.0-1031.35~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-aws-5.8-cloud-tools-5.8.0-1042",
            "binary_version": "5.8.0-1042.44~20.04.1"
          },
          {
            "binary_name": "linux-aws-5.8-headers-5.8.0-1042",
            "binary_version": "5.8.0-1042.44~20.04.1"
          },
          {
            "binary_name": "linux-aws-5.8-tools-5.8.0-1042",
            "binary_version": "5.8.0-1042.44~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.8.0-1042-aws",
            "binary_version": "5.8.0-1042.44~20.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.8.0-1042-aws",
            "binary_version": "5.8.0-1042.44~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.8.0-1042-aws",
            "binary_version": "5.8.0-1042.44~20.04.1"
          },
          {
            "binary_name": "linux-image-5.8.0-1042-aws",
            "binary_version": "5.8.0-1042.44~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.8.0-1042-aws",
            "binary_version": "5.8.0-1042.44~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.8.0-1042-aws",
            "binary_version": "5.8.0-1042.44~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.8.0-1042-aws",
            "binary_version": "5.8.0-1042.44~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-aws-5.8",
        "purl": "pkg:deb/ubuntu/linux-aws-5.8@5.8.0-1042.44~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.8.0-1035.37~20.04.1",
        "5.8.0-1038.40~20.04.1",
        "5.8.0-1041.43~20.04.1",
        "5.8.0-1042.44~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-azure-5.11-cloud-tools-5.11.0-1028",
            "binary_version": "5.11.0-1028.31~20.04.2"
          },
          {
            "binary_name": "linux-azure-5.11-headers-5.11.0-1028",
            "binary_version": "5.11.0-1028.31~20.04.2"
          },
          {
            "binary_name": "linux-azure-5.11-tools-5.11.0-1028",
            "binary_version": "5.11.0-1028.31~20.04.2"
          },
          {
            "binary_name": "linux-buildinfo-5.11.0-1028-azure",
            "binary_version": "5.11.0-1028.31~20.04.2"
          },
          {
            "binary_name": "linux-cloud-tools-5.11.0-1028-azure",
            "binary_version": "5.11.0-1028.31~20.04.2"
          },
          {
            "binary_name": "linux-headers-5.11.0-1028-azure",
            "binary_version": "5.11.0-1028.31~20.04.2"
          },
          {
            "binary_name": "linux-image-unsigned-5.11.0-1028-azure",
            "binary_version": "5.11.0-1028.31~20.04.2"
          },
          {
            "binary_name": "linux-modules-5.11.0-1028-azure",
            "binary_version": "5.11.0-1028.31~20.04.2"
          },
          {
            "binary_name": "linux-modules-extra-5.11.0-1028-azure",
            "binary_version": "5.11.0-1028.31~20.04.2"
          },
          {
            "binary_name": "linux-tools-5.11.0-1028-azure",
            "binary_version": "5.11.0-1028.31~20.04.2"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-azure-5.11",
        "purl": "pkg:deb/ubuntu/linux-azure-5.11@5.11.0-1028.31~20.04.2?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.11.0-1007.7~20.04.2",
        "5.11.0-1012.13~20.04.1",
        "5.11.0-1013.14~20.04.1",
        "5.11.0-1015.16~20.04.1",
        "5.11.0-1017.18~20.04.1",
        "5.11.0-1019.20~20.04.1",
        "5.11.0-1020.21~20.04.1",
        "5.11.0-1021.22~20.04.1",
        "5.11.0-1022.23~20.04.1",
        "5.11.0-1023.24~20.04.1",
        "5.11.0-1025.27~20.04.1",
        "5.11.0-1027.30~20.04.1",
        "5.11.0-1028.31~20.04.2"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-azure-5.13-cloud-tools-5.13.0-1031",
            "binary_version": "5.13.0-1031.37~20.04.1"
          },
          {
            "binary_name": "linux-azure-5.13-headers-5.13.0-1031",
            "binary_version": "5.13.0-1031.37~20.04.1"
          },
          {
            "binary_name": "linux-azure-5.13-tools-5.13.0-1031",
            "binary_version": "5.13.0-1031.37~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.13.0-1031-azure",
            "binary_version": "5.13.0-1031.37~20.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.13.0-1031-azure",
            "binary_version": "5.13.0-1031.37~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.13.0-1031-azure",
            "binary_version": "5.13.0-1031.37~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.13.0-1031-azure",
            "binary_version": "5.13.0-1031.37~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.13.0-1031-azure",
            "binary_version": "5.13.0-1031.37~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.13.0-1031-azure",
            "binary_version": "5.13.0-1031.37~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.13.0-1031-azure",
            "binary_version": "5.13.0-1031.37~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-azure-5.13",
        "purl": "pkg:deb/ubuntu/linux-azure-5.13@5.13.0-1031.37~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.13.0-1009.10~20.04.2",
        "5.13.0-1012.14~20.04.1",
        "5.13.0-1013.15~20.04.1",
        "5.13.0-1014.16~20.04.1",
        "5.13.0-1017.19~20.04.1",
        "5.13.0-1021.24~20.04.1",
        "5.13.0-1022.26~20.04.1",
        "5.13.0-1023.27~20.04.1",
        "5.13.0-1025.29~20.04.1",
        "5.13.0-1028.33~20.04.1",
        "5.13.0-1029.34~20.04.1",
        "5.13.0-1031.37~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-azure-5.8-cloud-tools-5.8.0-1043",
            "binary_version": "5.8.0-1043.46~20.04.1"
          },
          {
            "binary_name": "linux-azure-5.8-headers-5.8.0-1043",
            "binary_version": "5.8.0-1043.46~20.04.1"
          },
          {
            "binary_name": "linux-azure-5.8-tools-5.8.0-1043",
            "binary_version": "5.8.0-1043.46~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.8.0-1043-azure",
            "binary_version": "5.8.0-1043.46~20.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.8.0-1043-azure",
            "binary_version": "5.8.0-1043.46~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.8.0-1043-azure",
            "binary_version": "5.8.0-1043.46~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.8.0-1043-azure",
            "binary_version": "5.8.0-1043.46~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.8.0-1043-azure",
            "binary_version": "5.8.0-1043.46~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.8.0-1043-azure",
            "binary_version": "5.8.0-1043.46~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.8.0-1043-azure",
            "binary_version": "5.8.0-1043.46~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-azure-5.8",
        "purl": "pkg:deb/ubuntu/linux-azure-5.8@5.8.0-1043.46~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.8.0-1033.35~20.04.1",
        "5.8.0-1036.38~20.04.1",
        "5.8.0-1039.42~20.04.1",
        "5.8.0-1040.43~20.04.1",
        "5.8.0-1041.44~20.04.1",
        "5.8.0-1042.45~20.04.1",
        "5.8.0-1043.46~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-unsigned-5.4.0-1103-azure-fde",
            "binary_version": "5.4.0-1103.109+cvm1.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-azure-fde",
        "purl": "pkg:deb/ubuntu/linux-azure-fde@5.4.0-1103.109+cvm1.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.4.0-1063.66+cvm2.2",
        "5.4.0-1063.66+cvm3.2",
        "5.4.0-1064.67+cvm1.1",
        "5.4.0-1065.68+cvm2.1",
        "5.4.0-1067.70+cvm1.1",
        "5.4.0-1068.71+cvm1.1",
        "5.4.0-1069.72+cvm1.1",
        "5.4.0-1070.73+cvm1.1",
        "5.4.0-1072.75+cvm1.1",
        "5.4.0-1073.76+cvm1.1",
        "5.4.0-1074.77+cvm1.1",
        "5.4.0-1076.79+cvm1.1",
        "5.4.0-1078.81+cvm1.1",
        "5.4.0-1080.83+cvm1.1",
        "5.4.0-1083.87+cvm1.1",
        "5.4.0-1085.90+cvm1.1",
        "5.4.0-1085.90+cvm2.1",
        "5.4.0-1086.91+cvm1.1",
        "5.4.0-1089.94+cvm1.2",
        "5.4.0-1090.95+cvm1.1",
        "5.4.0-1091.96+cvm1.1",
        "5.4.0-1092.97+cvm1.1",
        "5.4.0-1095.101+cvm1.1",
        "5.4.0-1098.104+cvm1.1",
        "5.4.0-1100.106+cvm1.1",
        "5.4.0-1103.109+cvm1.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.11.0-1029-gcp",
            "binary_version": "5.11.0-1029.33~20.04.3"
          },
          {
            "binary_name": "linux-gcp-5.11-headers-5.11.0-1029",
            "binary_version": "5.11.0-1029.33~20.04.3"
          },
          {
            "binary_name": "linux-gcp-5.11-tools-5.11.0-1029",
            "binary_version": "5.11.0-1029.33~20.04.3"
          },
          {
            "binary_name": "linux-headers-5.11.0-1029-gcp",
            "binary_version": "5.11.0-1029.33~20.04.3"
          },
          {
            "binary_name": "linux-image-unsigned-5.11.0-1029-gcp",
            "binary_version": "5.11.0-1029.33~20.04.3"
          },
          {
            "binary_name": "linux-modules-5.11.0-1029-gcp",
            "binary_version": "5.11.0-1029.33~20.04.3"
          },
          {
            "binary_name": "linux-modules-extra-5.11.0-1029-gcp",
            "binary_version": "5.11.0-1029.33~20.04.3"
          },
          {
            "binary_name": "linux-tools-5.11.0-1029-gcp",
            "binary_version": "5.11.0-1029.33~20.04.3"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-gcp-5.11",
        "purl": "pkg:deb/ubuntu/linux-gcp-5.11@5.11.0-1029.33~20.04.3?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.11.0-1009.10~20.04.1",
        "5.11.0-1014.16~20.04.1",
        "5.11.0-1017.19~20.04.1",
        "5.11.0-1018.20~20.04.2",
        "5.11.0-1020.22~20.04.1",
        "5.11.0-1021.23~20.04.1",
        "5.11.0-1022.24~20.04.1",
        "5.11.0-1023.25~20.04.1",
        "5.11.0-1024.26~20.04.1",
        "5.11.0-1026.29~20.04.1",
        "5.11.0-1028.32~20.04.1",
        "5.11.0-1029.33~20.04.3"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.13.0-1033-gcp",
            "binary_version": "5.13.0-1033.40~20.04.1"
          },
          {
            "binary_name": "linux-gcp-5.13-headers-5.13.0-1033",
            "binary_version": "5.13.0-1033.40~20.04.1"
          },
          {
            "binary_name": "linux-gcp-5.13-tools-5.13.0-1033",
            "binary_version": "5.13.0-1033.40~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.13.0-1033-gcp",
            "binary_version": "5.13.0-1033.40~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.13.0-1033-gcp",
            "binary_version": "5.13.0-1033.40~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.13.0-1033-gcp",
            "binary_version": "5.13.0-1033.40~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.13.0-1033-gcp",
            "binary_version": "5.13.0-1033.40~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.13.0-1033-gcp",
            "binary_version": "5.13.0-1033.40~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-gcp-5.13",
        "purl": "pkg:deb/ubuntu/linux-gcp-5.13@5.13.0-1033.40~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.13.0-1008.9~20.04.3",
        "5.13.0-1012.15~20.04.1",
        "5.13.0-1013.16~20.04.1",
        "5.13.0-1015.18~20.04.1",
        "5.13.0-1019.23~20.04.1",
        "5.13.0-1021.25~20.04.1",
        "5.13.0-1023.28~20.04.1",
        "5.13.0-1024.29~20.04.1",
        "5.13.0-1025.30~20.04.1",
        "5.13.0-1027.32~20.04.1",
        "5.13.0-1030.36~20.04.1",
        "5.13.0-1031.37~20.04.1",
        "5.13.0-1033.40~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.8.0-1039-gcp",
            "binary_version": "5.8.0-1039.41"
          },
          {
            "binary_name": "linux-gcp-5.8-headers-5.8.0-1039",
            "binary_version": "5.8.0-1039.41"
          },
          {
            "binary_name": "linux-gcp-5.8-tools-5.8.0-1039",
            "binary_version": "5.8.0-1039.41"
          },
          {
            "binary_name": "linux-headers-5.8.0-1039-gcp",
            "binary_version": "5.8.0-1039.41"
          },
          {
            "binary_name": "linux-image-unsigned-5.8.0-1039-gcp",
            "binary_version": "5.8.0-1039.41"
          },
          {
            "binary_name": "linux-modules-5.8.0-1039-gcp",
            "binary_version": "5.8.0-1039.41"
          },
          {
            "binary_name": "linux-modules-extra-5.8.0-1039-gcp",
            "binary_version": "5.8.0-1039.41"
          },
          {
            "binary_name": "linux-tools-5.8.0-1039-gcp",
            "binary_version": "5.8.0-1039.41"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-gcp-5.8",
        "purl": "pkg:deb/ubuntu/linux-gcp-5.8@5.8.0-1039.41?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.8.0-1032.34~20.04.1",
        "5.8.0-1035.37~20.04.1",
        "5.8.0-1038.40~20.04.1",
        "5.8.0-1039.41"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.4.0-1105-gke",
            "binary_version": "5.4.0-1105.112"
          },
          {
            "binary_name": "linux-gke-headers-5.4.0-1105",
            "binary_version": "5.4.0-1105.112"
          },
          {
            "binary_name": "linux-gke-tools-5.4.0-1105",
            "binary_version": "5.4.0-1105.112"
          },
          {
            "binary_name": "linux-headers-5.4.0-1105-gke",
            "binary_version": "5.4.0-1105.112"
          },
          {
            "binary_name": "linux-image-unsigned-5.4.0-1105-gke",
            "binary_version": "5.4.0-1105.112"
          },
          {
            "binary_name": "linux-modules-5.4.0-1105-gke",
            "binary_version": "5.4.0-1105.112"
          },
          {
            "binary_name": "linux-modules-extra-5.4.0-1105-gke",
            "binary_version": "5.4.0-1105.112"
          },
          {
            "binary_name": "linux-tools-5.4.0-1105-gke",
            "binary_version": "5.4.0-1105.112"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-gke",
        "purl": "pkg:deb/ubuntu/linux-gke@5.4.0-1105.112?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.4.0-1033.35",
        "5.4.0-1035.37",
        "5.4.0-1036.38",
        "5.4.0-1037.39",
        "5.4.0-1039.41",
        "5.4.0-1041.43",
        "5.4.0-1042.44",
        "5.4.0-1043.45",
        "5.4.0-1044.46",
        "5.4.0-1046.48",
        "5.4.0-1049.52",
        "5.4.0-1051.54",
        "5.4.0-1052.55",
        "5.4.0-1053.56",
        "5.4.0-1054.57",
        "5.4.0-1055.58",
        "5.4.0-1056.59",
        "5.4.0-1057.60",
        "5.4.0-1059.62",
        "5.4.0-1061.64",
        "5.4.0-1062.65",
        "5.4.0-1063.66",
        "5.4.0-1065.68",
        "5.4.0-1066.69",
        "5.4.0-1067.70",
        "5.4.0-1068.71",
        "5.4.0-1071.76",
        "5.4.0-1072.77",
        "5.4.0-1074.79",
        "5.4.0-1076.82",
        "5.4.0-1078.84",
        "5.4.0-1080.86",
        "5.4.0-1081.87",
        "5.4.0-1083.89",
        "5.4.0-1084.90",
        "5.4.0-1086.93",
        "5.4.0-1087.94",
        "5.4.0-1090.97",
        "5.4.0-1091.98",
        "5.4.0-1094.101",
        "5.4.0-1095.102",
        "5.4.0-1096.103",
        "5.4.0-1097.104",
        "5.4.0-1098.105",
        "5.4.0-1099.106",
        "5.4.0-1100.107",
        "5.4.0-1101.108",
        "5.4.0-1102.109",
        "5.4.0-1103.110",
        "5.4.0-1104.111",
        "5.4.0-1105.112"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1039-gke",
            "binary_version": "5.15.0-1039.44~20.04.1"
          },
          {
            "binary_name": "linux-gke-5.15-headers-5.15.0-1039",
            "binary_version": "5.15.0-1039.44~20.04.1"
          },
          {
            "binary_name": "linux-gke-5.15-tools-5.15.0-1039",
            "binary_version": "5.15.0-1039.44~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.15.0-1039-gke",
            "binary_version": "5.15.0-1039.44~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1039-gke",
            "binary_version": "5.15.0-1039.44~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.15.0-1039-gke",
            "binary_version": "5.15.0-1039.44~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1039-gke",
            "binary_version": "5.15.0-1039.44~20.04.1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-5.15.0-1039-gke",
            "binary_version": "5.15.0-1039.44~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.15.0-1039-gke",
            "binary_version": "5.15.0-1039.44~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-gke-5.15",
        "purl": "pkg:deb/ubuntu/linux-gke-5.15@5.15.0-1039.44~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1011.14~20.04.1",
        "5.15.0-1014.17~20.04.1",
        "5.15.0-1015.18~20.04.1",
        "5.15.0-1016.19~20.04.1",
        "5.15.0-1019.23~20.04.1",
        "5.15.0-1020.25~20.04.1",
        "5.15.0-1023.28~20.04.2",
        "5.15.0-1027.32~20.04.1",
        "5.15.0-1028.33~20.04.1",
        "5.15.0-1029.34~20.04.1",
        "5.15.0-1031.36~20.04.1",
        "5.15.0-1032.37~20.04.1",
        "5.15.0-1033.38~20.04.1",
        "5.15.0-1034.39~20.04.1",
        "5.15.0-1036.41~20.04.1",
        "5.15.0-1037.42~20.04.1",
        "5.15.0-1038.43~20.04.1",
        "5.15.0-1039.44~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.4.0-1102-gkeop",
            "binary_version": "5.4.0-1102.106"
          },
          {
            "binary_name": "linux-cloud-tools-5.4.0-1102-gkeop",
            "binary_version": "5.4.0-1102.106"
          },
          {
            "binary_name": "linux-gkeop-cloud-tools-5.4.0-1102",
            "binary_version": "5.4.0-1102.106"
          },
          {
            "binary_name": "linux-gkeop-headers-5.4.0-1102",
            "binary_version": "5.4.0-1102.106"
          },
          {
            "binary_name": "linux-gkeop-source-5.4.0",
            "binary_version": "5.4.0-1102.106"
          },
          {
            "binary_name": "linux-gkeop-tools-5.4.0-1102",
            "binary_version": "5.4.0-1102.106"
          },
          {
            "binary_name": "linux-headers-5.4.0-1102-gkeop",
            "binary_version": "5.4.0-1102.106"
          },
          {
            "binary_name": "linux-image-unsigned-5.4.0-1102-gkeop",
            "binary_version": "5.4.0-1102.106"
          },
          {
            "binary_name": "linux-modules-5.4.0-1102-gkeop",
            "binary_version": "5.4.0-1102.106"
          },
          {
            "binary_name": "linux-modules-extra-5.4.0-1102-gkeop",
            "binary_version": "5.4.0-1102.106"
          },
          {
            "binary_name": "linux-tools-5.4.0-1102-gkeop",
            "binary_version": "5.4.0-1102.106"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-gkeop",
        "purl": "pkg:deb/ubuntu/linux-gkeop@5.4.0-1102.106?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.4.0-1008.9",
        "5.4.0-1009.10",
        "5.4.0-1010.11",
        "5.4.0-1011.12",
        "5.4.0-1012.13",
        "5.4.0-1013.14",
        "5.4.0-1014.15",
        "5.4.0-1015.16",
        "5.4.0-1016.17",
        "5.4.0-1018.19",
        "5.4.0-1021.22",
        "5.4.0-1022.23",
        "5.4.0-1023.24",
        "5.4.0-1024.25",
        "5.4.0-1025.26",
        "5.4.0-1026.27",
        "5.4.0-1027.28",
        "5.4.0-1029.30",
        "5.4.0-1031.32",
        "5.4.0-1032.33",
        "5.4.0-1033.34",
        "5.4.0-1034.35",
        "5.4.0-1036.37",
        "5.4.0-1037.38",
        "5.4.0-1038.39",
        "5.4.0-1039.40",
        "5.4.0-1040.41",
        "5.4.0-1043.44",
        "5.4.0-1046.48",
        "5.4.0-1048.51",
        "5.4.0-1049.52",
        "5.4.0-1051.54",
        "5.4.0-1052.55",
        "5.4.0-1053.56",
        "5.4.0-1054.57",
        "5.4.0-1056.60",
        "5.4.0-1057.61",
        "5.4.0-1060.64",
        "5.4.0-1061.65",
        "5.4.0-1062.66",
        "5.4.0-1064.68",
        "5.4.0-1065.69",
        "5.4.0-1066.70",
        "5.4.0-1067.71",
        "5.4.0-1068.72",
        "5.4.0-1069.73",
        "5.4.0-1070.74",
        "5.4.0-1071.75",
        "5.4.0-1072.76",
        "5.4.0-1073.77",
        "5.4.0-1074.78",
        "5.4.0-1075.79",
        "5.4.0-1076.80",
        "5.4.0-1077.81",
        "5.4.0-1078.82",
        "5.4.0-1079.83",
        "5.4.0-1080.84",
        "5.4.0-1081.85",
        "5.4.0-1083.87",
        "5.4.0-1084.88",
        "5.4.0-1085.89",
        "5.4.0-1086.90",
        "5.4.0-1087.91",
        "5.4.0-1088.92",
        "5.4.0-1089.93",
        "5.4.0-1090.94",
        "5.4.0-1091.95",
        "5.4.0-1092.96",
        "5.4.0-1093.97",
        "5.4.0-1094.98",
        "5.4.0-1095.99",
        "5.4.0-1096.100",
        "5.4.0-1097.101",
        "5.4.0-1098.102",
        "5.4.0-1099.103",
        "5.4.0-1100.104",
        "5.4.0-1101.105",
        "5.4.0-1102.106"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1055-gkeop",
            "binary_version": "5.15.0-1055.62~20.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-1055-gkeop",
            "binary_version": "5.15.0-1055.62~20.04.1"
          },
          {
            "binary_name": "linux-gkeop-5.15-cloud-tools-5.15.0-1055",
            "binary_version": "5.15.0-1055.62~20.04.1"
          },
          {
            "binary_name": "linux-gkeop-5.15-headers-5.15.0-1055",
            "binary_version": "5.15.0-1055.62~20.04.1"
          },
          {
            "binary_name": "linux-gkeop-5.15-tools-5.15.0-1055",
            "binary_version": "5.15.0-1055.62~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.15.0-1055-gkeop",
            "binary_version": "5.15.0-1055.62~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1055-gkeop",
            "binary_version": "5.15.0-1055.62~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.15.0-1055-gkeop",
            "binary_version": "5.15.0-1055.62~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1055-gkeop",
            "binary_version": "5.15.0-1055.62~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.15.0-1055-gkeop",
            "binary_version": "5.15.0-1055.62~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-gkeop-5.15",
        "purl": "pkg:deb/ubuntu/linux-gkeop-5.15@5.15.0-1055.62~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1003.5~20.04.2",
        "5.15.0-1005.7~20.04.1",
        "5.15.0-1007.10~20.04.1",
        "5.15.0-1008.12~20.04.1",
        "5.15.0-1011.15~20.04.2",
        "5.15.0-1012.16~20.04.1",
        "5.15.0-1013.17~20.04.1",
        "5.15.0-1015.19~20.04.1",
        "5.15.0-1016.21~20.04.1",
        "5.15.0-1017.22~20.04.1",
        "5.15.0-1018.23~20.04.1",
        "5.15.0-1019.24~20.04.1",
        "5.15.0-1020.25~20.04.1",
        "5.15.0-1021.26~20.04.1",
        "5.15.0-1022.27~20.04.1",
        "5.15.0-1023.28~20.04.1",
        "5.15.0-1024.29~20.04.1",
        "5.15.0-1025.30~20.04.1",
        "5.15.0-1026.31~20.04.1",
        "5.15.0-1027.32~20.04.1",
        "5.15.0-1028.33~20.04.1",
        "5.15.0-1030.35~20.04.1",
        "5.15.0-1031.37~20.04.1",
        "5.15.0-1032.38~20.04.1",
        "5.15.0-1033.39~20.04.1",
        "5.15.0-1034.40~20.04.1",
        "5.15.0-1035.41~20.04.1",
        "5.15.0-1036.42~20.04.1",
        "5.15.0-1037.43~20.04.1",
        "5.15.0-1038.44~20.04.1",
        "5.15.0-1039.45~20.04.1",
        "5.15.0-1040.46~20.04.1",
        "5.15.0-1043.50~20.04.1",
        "5.15.0-1044.51~20.04.1",
        "5.15.0-1045.52~20.04.1",
        "5.15.0-1046.53~20.04.1",
        "5.15.0-1047.54~20.04.1",
        "5.15.0-1048.55~20.04.1",
        "5.15.0-1049.56~20.04.1",
        "5.15.0-1050.57~20.04.1",
        "5.15.0-1051.58~20.04.1",
        "5.15.0-1052.59~20.04.1",
        "5.15.0-1053.60~20.04.1",
        "5.15.0-1054.61~20.04.1",
        "5.15.0-1055.62~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "block-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "block-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "block-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "crypto-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "crypto-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "crypto-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "dasd-extra-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "dasd-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "fat-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "fat-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "fat-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "fb-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "firewire-core-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "floppy-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "fs-core-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "fs-core-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "fs-core-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "fs-secondary-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "fs-secondary-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "fs-secondary-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "input-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "input-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "input-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "ipmi-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "ipmi-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "ipmi-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "kernel-image-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "kernel-image-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "kernel-image-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.11.0-46-generic",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.11.0-46-generic-64k",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.11.0-46-generic-lpae",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.11.0-46-lowlatency",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.11.0-46-generic",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.11.0-46-lowlatency",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.11.0-46-generic",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.11.0-46-generic-64k",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.11.0-46-generic-lpae",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.11.0-46-lowlatency",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.11-cloud-tools-5.11.0-46",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.11-cloud-tools-common",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.11-headers-5.11.0-46",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.11-source-5.11.0",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.11-tools-5.11.0-46",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.11-tools-common",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.11-tools-host",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.11-udebs-generic",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.11-udebs-generic-64k",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.11-udebs-generic-lpae",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-image-5.11.0-46-generic",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-image-5.11.0-46-generic-lpae",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.11.0-46-generic",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.11.0-46-generic-64k",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.11.0-46-lowlatency",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.11.0-46-generic",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.11.0-46-generic-64k",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.11.0-46-generic-lpae",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.11.0-46-lowlatency",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.11.0-46-generic",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.11.0-46-generic",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.11.0-46-generic-64k",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.11.0-46-generic-lpae",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.11.0-46-lowlatency",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "md-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "md-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "md-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "message-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "message-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "mouse-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "mouse-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "mouse-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "multipath-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "multipath-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "multipath-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "nfs-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "nfs-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "nfs-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "nic-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "nic-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "nic-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "nic-pcmcia-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "nic-shared-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "nic-shared-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "nic-shared-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "nic-usb-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "nic-usb-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "nic-usb-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "parport-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "parport-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "parport-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "pata-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "pcmcia-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "pcmcia-storage-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "plip-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "plip-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "plip-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "ppp-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "ppp-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "ppp-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "sata-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "sata-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "sata-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "scsi-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "scsi-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "scsi-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "serial-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "storage-core-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "storage-core-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "storage-core-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "usb-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "usb-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "usb-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "virtio-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "virtio-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "vlan-modules-5.11.0-46-generic-64k-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "vlan-modules-5.11.0-46-generic-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          },
          {
            "binary_name": "vlan-modules-5.11.0-46-generic-lpae-di",
            "binary_version": "5.11.0-46.51~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-hwe-5.11",
        "purl": "pkg:deb/ubuntu/linux-hwe-5.11@5.11.0-46.51~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.11.0-22.23~20.04.1",
        "5.11.0-25.27~20.04.1",
        "5.11.0-27.29~20.04.1",
        "5.11.0-34.36~20.04.1",
        "5.11.0-36.40~20.04.1",
        "5.11.0-37.41~20.04.2",
        "5.11.0-38.42~20.04.1",
        "5.11.0-40.44~20.04.2",
        "5.11.0-41.45~20.04.1",
        "5.11.0-43.47~20.04.2",
        "5.11.0-44.48~20.04.2",
        "5.11.0-46.51~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "block-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "block-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "block-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "crypto-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "crypto-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "crypto-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "dasd-extra-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "dasd-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "fat-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "fat-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "fat-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "fb-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "firewire-core-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "floppy-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "fs-core-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "fs-core-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "fs-core-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "fs-secondary-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "fs-secondary-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "fs-secondary-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "input-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "input-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "input-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "ipmi-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "ipmi-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "ipmi-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "kernel-image-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "kernel-image-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "kernel-image-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.13.0-52-generic",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.13.0-52-generic-64k",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.13.0-52-generic-lpae",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.13.0-52-lowlatency",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.13.0-52-generic",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.13.0-52-lowlatency",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.13.0-52-generic",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.13.0-52-generic-64k",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.13.0-52-generic-lpae",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.13.0-52-lowlatency",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.13-cloud-tools-5.13.0-52",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.13-cloud-tools-common",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.13-headers-5.13.0-52",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.13-source-5.13.0",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.13-tools-5.13.0-52",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.13-tools-common",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.13-tools-host",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.13-udebs-generic",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.13-udebs-generic-64k",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.13-udebs-generic-lpae",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-image-5.13.0-52-generic",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-image-5.13.0-52-generic-lpae",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.13.0-52-generic",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.13.0-52-generic-64k",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.13.0-52-lowlatency",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.13.0-52-generic",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.13.0-52-generic-64k",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.13.0-52-generic-lpae",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.13.0-52-lowlatency",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.13.0-52-generic",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.13.0-52-generic",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.13.0-52-generic-64k",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.13.0-52-generic-lpae",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.13.0-52-lowlatency",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "md-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "md-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "md-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "message-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "message-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "mouse-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "mouse-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "mouse-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "multipath-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "multipath-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "multipath-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "nfs-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "nfs-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "nfs-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "nic-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "nic-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "nic-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "nic-pcmcia-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "nic-shared-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "nic-shared-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "nic-shared-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "nic-usb-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "nic-usb-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "nic-usb-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "parport-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "parport-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "parport-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "pata-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "pcmcia-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "pcmcia-storage-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "plip-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "plip-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "plip-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "ppp-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "ppp-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "ppp-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "sata-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "sata-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "sata-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "scsi-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "scsi-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "scsi-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "serial-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "storage-core-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "storage-core-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "storage-core-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "usb-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "usb-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "usb-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "virtio-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "virtio-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "vlan-modules-5.13.0-52-generic-64k-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "vlan-modules-5.13.0-52-generic-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          },
          {
            "binary_name": "vlan-modules-5.13.0-52-generic-lpae-di",
            "binary_version": "5.13.0-52.59~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-hwe-5.13",
        "purl": "pkg:deb/ubuntu/linux-hwe-5.13@5.13.0-52.59~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.13.0-21.21~20.04.1",
        "5.13.0-22.22~20.04.1",
        "5.13.0-23.23~20.04.2",
        "5.13.0-25.26~20.04.1",
        "5.13.0-27.29~20.04.1",
        "5.13.0-28.31~20.04.1",
        "5.13.0-30.33~20.04.1",
        "5.13.0-35.40~20.04.1",
        "5.13.0-37.42~20.04.1",
        "5.13.0-39.44~20.04.1",
        "5.13.0-40.45~20.04.1",
        "5.13.0-41.46~20.04.1",
        "5.13.0-44.49~20.04.1",
        "5.13.0-48.54~20.04.1",
        "5.13.0-51.58~20.04.1",
        "5.13.0-52.59~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "block-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "block-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "block-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "crypto-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "crypto-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "crypto-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "dasd-extra-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "dasd-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "fat-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "fat-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "fat-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "fb-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "firewire-core-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "floppy-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "fs-core-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "fs-core-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "fs-core-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "fs-secondary-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "fs-secondary-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "fs-secondary-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "input-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "input-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "input-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "ipmi-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "ipmi-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "ipmi-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "kernel-image-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "kernel-image-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "kernel-image-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.8.0-63-generic",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.8.0-63-generic-64k",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.8.0-63-generic-lpae",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.8.0-63-lowlatency",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.8.0-63-generic",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.8.0-63-lowlatency",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.8.0-63-generic",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.8.0-63-generic-64k",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.8.0-63-generic-lpae",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.8.0-63-lowlatency",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.8-cloud-tools-5.8.0-63",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.8-cloud-tools-common",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.8-headers-5.8.0-63",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.8-source-5.8.0",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.8-tools-5.8.0-63",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.8-tools-common",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.8-tools-host",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.8-udebs-generic",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.8-udebs-generic-64k",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-hwe-5.8-udebs-generic-lpae",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-image-5.8.0-63-generic",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-image-5.8.0-63-generic-lpae",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.8.0-63-generic",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.8.0-63-generic-64k",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.8.0-63-lowlatency",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.8.0-63-generic",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.8.0-63-generic-64k",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.8.0-63-generic-lpae",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.8.0-63-lowlatency",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.8.0-63-generic",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.8.0-63-generic",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.8.0-63-generic-64k",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.8.0-63-generic-lpae",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.8.0-63-lowlatency",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "md-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "md-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "md-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "message-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "message-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "mouse-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "mouse-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "mouse-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "multipath-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "multipath-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "multipath-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "nfs-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "nfs-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "nfs-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "nic-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "nic-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "nic-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "nic-pcmcia-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "nic-shared-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "nic-shared-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "nic-shared-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "nic-usb-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "nic-usb-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "nic-usb-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "parport-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "parport-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "parport-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "pata-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "pcmcia-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "pcmcia-storage-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "plip-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "plip-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "plip-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "ppp-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "ppp-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "ppp-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "sata-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "sata-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "sata-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "scsi-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "scsi-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "scsi-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "serial-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "storage-core-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "storage-core-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "storage-core-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "usb-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "usb-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "usb-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "virtio-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "virtio-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "vlan-modules-5.8.0-63-generic-64k-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "vlan-modules-5.8.0-63-generic-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          },
          {
            "binary_name": "vlan-modules-5.8.0-63-generic-lpae-di",
            "binary_version": "5.8.0-63.71~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-hwe-5.8",
        "purl": "pkg:deb/ubuntu/linux-hwe-5.8@5.8.0-63.71~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.8.0-23.24~20.04.1",
        "5.8.0-25.26~20.04.1",
        "5.8.0-28.30~20.04.1",
        "5.8.0-29.31~20.04.1",
        "5.8.0-31.33~20.04.1",
        "5.8.0-33.36~20.04.1",
        "5.8.0-34.37~20.04.2",
        "5.8.0-36.40~20.04.1",
        "5.8.0-38.43~20.04.1",
        "5.8.0-40.45~20.04.1",
        "5.8.0-41.46~20.04.1",
        "5.8.0-43.49~20.04.1",
        "5.8.0-44.50~20.04.1",
        "5.8.0-45.51~20.04.1",
        "5.8.0-48.54~20.04.1",
        "5.8.0-49.55~20.04.1",
        "5.8.0-50.56~20.04.1",
        "5.8.0-53.60~20.04.1",
        "5.8.0-55.62~20.04.1",
        "5.8.0-59.66~20.04.1",
        "5.8.0-63.71~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.13.0-1017-intel",
            "binary_version": "5.13.0-1017.19"
          },
          {
            "binary_name": "linux-cloud-tools-5.13.0-1017-intel",
            "binary_version": "5.13.0-1017.19"
          },
          {
            "binary_name": "linux-headers-5.13.0-1017-intel",
            "binary_version": "5.13.0-1017.19"
          },
          {
            "binary_name": "linux-image-unsigned-5.13.0-1017-intel",
            "binary_version": "5.13.0-1017.19"
          },
          {
            "binary_name": "linux-intel-5.13-cloud-tools-5.13.0-1017",
            "binary_version": "5.13.0-1017.19"
          },
          {
            "binary_name": "linux-intel-5.13-cloud-tools-common",
            "binary_version": "5.13.0-1017.19"
          },
          {
            "binary_name": "linux-intel-5.13-headers-5.13.0-1017",
            "binary_version": "5.13.0-1017.19"
          },
          {
            "binary_name": "linux-intel-5.13-source-5.13.0",
            "binary_version": "5.13.0-1017.19"
          },
          {
            "binary_name": "linux-intel-5.13-tools-5.13.0-1017",
            "binary_version": "5.13.0-1017.19"
          },
          {
            "binary_name": "linux-intel-5.13-tools-common",
            "binary_version": "5.13.0-1017.19"
          },
          {
            "binary_name": "linux-intel-5.13-tools-host",
            "binary_version": "5.13.0-1017.19"
          },
          {
            "binary_name": "linux-modules-5.13.0-1017-intel",
            "binary_version": "5.13.0-1017.19"
          },
          {
            "binary_name": "linux-modules-extra-5.13.0-1017-intel",
            "binary_version": "5.13.0-1017.19"
          },
          {
            "binary_name": "linux-tools-5.13.0-1017-intel",
            "binary_version": "5.13.0-1017.19"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-intel-5.13",
        "purl": "pkg:deb/ubuntu/linux-intel-5.13@5.13.0-1017.19?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.13.0-1007.7",
        "5.13.0-1008.8",
        "5.13.0-1009.9",
        "5.13.0-1010.10",
        "5.13.0-1011.11",
        "5.13.0-1014.15",
        "5.13.0-1017.19"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.10.0-1057-oem",
            "binary_version": "5.10.0-1057.61"
          },
          {
            "binary_name": "linux-headers-5.10.0-1057-oem",
            "binary_version": "5.10.0-1057.61"
          },
          {
            "binary_name": "linux-image-unsigned-5.10.0-1057-oem",
            "binary_version": "5.10.0-1057.61"
          },
          {
            "binary_name": "linux-modules-5.10.0-1057-oem",
            "binary_version": "5.10.0-1057.61"
          },
          {
            "binary_name": "linux-oem-5.10-headers-5.10.0-1057",
            "binary_version": "5.10.0-1057.61"
          },
          {
            "binary_name": "linux-oem-5.10-tools-5.10.0-1057",
            "binary_version": "5.10.0-1057.61"
          },
          {
            "binary_name": "linux-oem-5.10-tools-host",
            "binary_version": "5.10.0-1057.61"
          },
          {
            "binary_name": "linux-tools-5.10.0-1057-oem",
            "binary_version": "5.10.0-1057.61"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-oem-5.10",
        "purl": "pkg:deb/ubuntu/linux-oem-5.10@5.10.0-1057.61?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.10.0-1008.9",
        "5.10.0-1011.12",
        "5.10.0-1013.14",
        "5.10.0-1014.15",
        "5.10.0-1016.17",
        "5.10.0-1017.18",
        "5.10.0-1019.20",
        "5.10.0-1021.22",
        "5.10.0-1022.23",
        "5.10.0-1023.24",
        "5.10.0-1025.26",
        "5.10.0-1026.27",
        "5.10.0-1029.30",
        "5.10.0-1032.33",
        "5.10.0-1033.34",
        "5.10.0-1034.35",
        "5.10.0-1038.40",
        "5.10.0-1044.46",
        "5.10.0-1045.47",
        "5.10.0-1049.51",
        "5.10.0-1050.52",
        "5.10.0-1051.53",
        "5.10.0-1052.54",
        "5.10.0-1053.55",
        "5.10.0-1055.58",
        "5.10.0-1057.61"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.13.0-1029-oem",
            "binary_version": "5.13.0-1029.36"
          },
          {
            "binary_name": "linux-headers-5.13.0-1029-oem",
            "binary_version": "5.13.0-1029.36"
          },
          {
            "binary_name": "linux-image-unsigned-5.13.0-1029-oem",
            "binary_version": "5.13.0-1029.36"
          },
          {
            "binary_name": "linux-modules-5.13.0-1029-oem",
            "binary_version": "5.13.0-1029.36"
          },
          {
            "binary_name": "linux-oem-5.13-headers-5.13.0-1029",
            "binary_version": "5.13.0-1029.36"
          },
          {
            "binary_name": "linux-oem-5.13-tools-5.13.0-1029",
            "binary_version": "5.13.0-1029.36"
          },
          {
            "binary_name": "linux-oem-5.13-tools-host",
            "binary_version": "5.13.0-1029.36"
          },
          {
            "binary_name": "linux-tools-5.13.0-1029-oem",
            "binary_version": "5.13.0-1029.36"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-oem-5.13",
        "purl": "pkg:deb/ubuntu/linux-oem-5.13@5.13.0-1029.36?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.13.0-1009.10",
        "5.13.0-1010.11",
        "5.13.0-1012.16",
        "5.13.0-1014.18",
        "5.13.0-1017.21",
        "5.13.0-1019.23",
        "5.13.0-1020.24",
        "5.13.0-1021.25",
        "5.13.0-1022.26",
        "5.13.0-1026.32",
        "5.13.0-1028.35",
        "5.13.0-1029.36"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.14.0-1059-oem",
            "binary_version": "5.14.0-1059.67"
          },
          {
            "binary_name": "linux-headers-5.14.0-1059-oem",
            "binary_version": "5.14.0-1059.67"
          },
          {
            "binary_name": "linux-image-unsigned-5.14.0-1059-oem",
            "binary_version": "5.14.0-1059.67"
          },
          {
            "binary_name": "linux-modules-5.14.0-1059-oem",
            "binary_version": "5.14.0-1059.67"
          },
          {
            "binary_name": "linux-modules-iwlwifi-5.14.0-1059-oem",
            "binary_version": "5.14.0-1059.67"
          },
          {
            "binary_name": "linux-oem-5.14-headers-5.14.0-1059",
            "binary_version": "5.14.0-1059.67"
          },
          {
            "binary_name": "linux-oem-5.14-tools-5.14.0-1059",
            "binary_version": "5.14.0-1059.67"
          },
          {
            "binary_name": "linux-oem-5.14-tools-host",
            "binary_version": "5.14.0-1059.67"
          },
          {
            "binary_name": "linux-tools-5.14.0-1059-oem",
            "binary_version": "5.14.0-1059.67"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-oem-5.14",
        "purl": "pkg:deb/ubuntu/linux-oem-5.14@5.14.0-1059.67?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.14.0-1004.4",
        "5.14.0-1005.5",
        "5.14.0-1007.7",
        "5.14.0-1008.8",
        "5.14.0-1010.10",
        "5.14.0-1011.11",
        "5.14.0-1013.13",
        "5.14.0-1018.19",
        "5.14.0-1020.22",
        "5.14.0-1022.24",
        "5.14.0-1024.26",
        "5.14.0-1027.30",
        "5.14.0-1029.32",
        "5.14.0-1031.34",
        "5.14.0-1032.35",
        "5.14.0-1033.36",
        "5.14.0-1034.37",
        "5.14.0-1036.40",
        "5.14.0-1038.42",
        "5.14.0-1042.47",
        "5.14.0-1044.49",
        "5.14.0-1045.51",
        "5.14.0-1046.53",
        "5.14.0-1047.54",
        "5.14.0-1048.55",
        "5.14.0-1049.56",
        "5.14.0-1050.57",
        "5.14.0-1051.58",
        "5.14.0-1052.59",
        "5.14.0-1054.61",
        "5.14.0-1055.62",
        "5.14.0-1056.63",
        "5.14.0-1057.64",
        "5.14.0-1058.66",
        "5.14.0-1059.67"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.6.0-1056-oem",
            "binary_version": "5.6.0-1056.60"
          },
          {
            "binary_name": "linux-headers-5.6.0-1056-oem",
            "binary_version": "5.6.0-1056.60"
          },
          {
            "binary_name": "linux-image-unsigned-5.6.0-1056-oem",
            "binary_version": "5.6.0-1056.60"
          },
          {
            "binary_name": "linux-modules-5.6.0-1056-oem",
            "binary_version": "5.6.0-1056.60"
          },
          {
            "binary_name": "linux-oem-5.6-headers-5.6.0-1056",
            "binary_version": "5.6.0-1056.60"
          },
          {
            "binary_name": "linux-oem-5.6-tools-5.6.0-1056",
            "binary_version": "5.6.0-1056.60"
          },
          {
            "binary_name": "linux-oem-5.6-tools-host",
            "binary_version": "5.6.0-1056.60"
          },
          {
            "binary_name": "linux-tools-5.6.0-1056-oem",
            "binary_version": "5.6.0-1056.60"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-oem-5.6",
        "purl": "pkg:deb/ubuntu/linux-oem-5.6@5.6.0-1056.60?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.6.0-1007.7",
        "5.6.0-1008.8",
        "5.6.0-1010.10",
        "5.6.0-1011.11",
        "5.6.0-1013.13",
        "5.6.0-1017.17",
        "5.6.0-1018.18",
        "5.6.0-1020.20",
        "5.6.0-1021.21",
        "5.6.0-1023.23",
        "5.6.0-1026.26",
        "5.6.0-1027.27",
        "5.6.0-1028.28",
        "5.6.0-1031.32",
        "5.6.0-1032.33",
        "5.6.0-1033.35",
        "5.6.0-1034.36",
        "5.6.0-1035.37",
        "5.6.0-1036.39",
        "5.6.0-1039.43",
        "5.6.0-1042.46",
        "5.6.0-1047.51",
        "5.6.0-1048.52",
        "5.6.0-1050.54",
        "5.6.0-1052.56",
        "5.6.0-1053.57",
        "5.6.0-1054.58",
        "5.6.0-1055.59",
        "5.6.0-1056.60"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.11.0-1028-oracle",
            "binary_version": "5.11.0-1028.31~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.11.0-1028-oracle",
            "binary_version": "5.11.0-1028.31~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.11.0-1028-oracle",
            "binary_version": "5.11.0-1028.31~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.11.0-1028-oracle",
            "binary_version": "5.11.0-1028.31~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.11.0-1028-oracle",
            "binary_version": "5.11.0-1028.31~20.04.1"
          },
          {
            "binary_name": "linux-oracle-5.11-headers-5.11.0-1028",
            "binary_version": "5.11.0-1028.31~20.04.1"
          },
          {
            "binary_name": "linux-oracle-5.11-tools-5.11.0-1028",
            "binary_version": "5.11.0-1028.31~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.11.0-1028-oracle",
            "binary_version": "5.11.0-1028.31~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-oracle-5.11",
        "purl": "pkg:deb/ubuntu/linux-oracle-5.11@5.11.0-1028.31~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.11.0-1008.8~20.04.1",
        "5.11.0-1013.14~20.04.1",
        "5.11.0-1016.17~20.04.1",
        "5.11.0-1017.18~20.04.1",
        "5.11.0-1019.20~20.04.1",
        "5.11.0-1020.21~20.04.1",
        "5.11.0-1021.22~20.04.1",
        "5.11.0-1022.23~20.04.1",
        "5.11.0-1023.24~20.04.1",
        "5.11.0-1025.27~20.04.1",
        "5.11.0-1027.30~20.04.1",
        "5.11.0-1028.31~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.13.0-1036-oracle",
            "binary_version": "5.13.0-1036.43~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.13.0-1036-oracle",
            "binary_version": "5.13.0-1036.43~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.13.0-1036-oracle",
            "binary_version": "5.13.0-1036.43~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.13.0-1036-oracle",
            "binary_version": "5.13.0-1036.43~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.13.0-1036-oracle",
            "binary_version": "5.13.0-1036.43~20.04.1"
          },
          {
            "binary_name": "linux-oracle-5.13-headers-5.13.0-1036",
            "binary_version": "5.13.0-1036.43~20.04.1"
          },
          {
            "binary_name": "linux-oracle-5.13-tools-5.13.0-1036",
            "binary_version": "5.13.0-1036.43~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.13.0-1036-oracle",
            "binary_version": "5.13.0-1036.43~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-oracle-5.13",
        "purl": "pkg:deb/ubuntu/linux-oracle-5.13@5.13.0-1036.43~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.13.0-1011.13~20.04.2",
        "5.13.0-1015.19~20.04.1",
        "5.13.0-1016.20~20.04.1",
        "5.13.0-1018.22~20.04.1",
        "5.13.0-1021.26~20.04.1",
        "5.13.0-1025.30~20.04.1",
        "5.13.0-1027.32~20.04.1",
        "5.13.0-1028.33~20.04.1",
        "5.13.0-1030.35~20.04.1",
        "5.13.0-1033.39~20.04.1",
        "5.13.0-1034.40~20.04.1",
        "5.13.0-1036.43~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.8.0-1038-oracle",
            "binary_version": "5.8.0-1038.39~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.8.0-1038-oracle",
            "binary_version": "5.8.0-1038.39~20.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.8.0-1038-oracle",
            "binary_version": "5.8.0-1038.39~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.8.0-1038-oracle",
            "binary_version": "5.8.0-1038.39~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.8.0-1038-oracle",
            "binary_version": "5.8.0-1038.39~20.04.1"
          },
          {
            "binary_name": "linux-oracle-5.8-headers-5.8.0-1038",
            "binary_version": "5.8.0-1038.39~20.04.1"
          },
          {
            "binary_name": "linux-oracle-5.8-tools-5.8.0-1038",
            "binary_version": "5.8.0-1038.39~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.8.0-1038-oracle",
            "binary_version": "5.8.0-1038.39~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-oracle-5.8",
        "purl": "pkg:deb/ubuntu/linux-oracle-5.8@5.8.0-1038.39~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.8.0-1031.32~20.04.2",
        "5.8.0-1033.34~20.04.1",
        "5.8.0-1034.35~20.04.2",
        "5.8.0-1037.38~20.04.1",
        "5.8.0-1038.39~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.4.0-1006-raspi2",
            "binary_version": "5.4.0-1006.6"
          },
          {
            "binary_name": "linux-headers-5.4.0-1006-raspi2",
            "binary_version": "5.4.0-1006.6"
          },
          {
            "binary_name": "linux-image-5.4.0-1006-raspi2",
            "binary_version": "5.4.0-1006.6"
          },
          {
            "binary_name": "linux-modules-5.4.0-1006-raspi2",
            "binary_version": "5.4.0-1006.6"
          },
          {
            "binary_name": "linux-raspi2-headers-5.4.0-1006",
            "binary_version": "5.4.0-1006.6"
          },
          {
            "binary_name": "linux-raspi2-tools-5.4.0-1006",
            "binary_version": "5.4.0-1006.6"
          },
          {
            "binary_name": "linux-tools-5.4.0-1006-raspi2",
            "binary_version": "5.4.0-1006.6"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-raspi2",
        "purl": "pkg:deb/ubuntu/linux-raspi2@5.4.0-1006.6?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.3.0-1007.8",
        "5.3.0-1014.16",
        "5.3.0-1015.17",
        "5.3.0-1017.19",
        "5.4.0-1004.4",
        "5.4.0-1006.6"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "block-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "crypto-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "fat-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "firewire-core-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "fs-core-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "fs-secondary-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "input-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "ipmi-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "kernel-image-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "linux-buildinfo-5.4.0-40-generic",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "linux-headers-5.4.0-40-generic",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "linux-image-5.4.0-40-generic",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "linux-modules-5.4.0-40-generic",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "linux-modules-extra-5.4.0-40-generic",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "linux-riscv-headers-5.4.0-40",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "linux-riscv-tools-5.4.0-40",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "linux-tools-5.4.0-40-generic",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "linux-udebs-generic",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "md-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "message-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "mouse-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "multipath-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "nfs-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "nic-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "nic-shared-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "nic-usb-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "parport-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "pata-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "plip-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "ppp-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "sata-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "scsi-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "storage-core-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "usb-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "virtio-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          },
          {
            "binary_name": "vlan-modules-5.4.0-40-generic-di",
            "binary_version": "5.4.0-40.45"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-riscv",
        "purl": "pkg:deb/ubuntu/linux-riscv@5.4.0-40.45?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.4.0-24.28",
        "5.4.0-26.30",
        "5.4.0-27.31",
        "5.4.0-28.32",
        "5.4.0-30.34",
        "5.4.0-31.35",
        "5.4.0-33.37",
        "5.4.0-34.38",
        "5.4.0-36.41",
        "5.4.0-37.42",
        "5.4.0-39.44",
        "5.4.0-40.45"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.11.0-1031-generic",
            "binary_version": "5.11.0-1031.35"
          },
          {
            "binary_name": "linux-headers-5.11.0-1031-generic",
            "binary_version": "5.11.0-1031.35"
          },
          {
            "binary_name": "linux-image-5.11.0-1031-generic",
            "binary_version": "5.11.0-1031.35"
          },
          {
            "binary_name": "linux-modules-5.11.0-1031-generic",
            "binary_version": "5.11.0-1031.35"
          },
          {
            "binary_name": "linux-modules-extra-5.11.0-1031-generic",
            "binary_version": "5.11.0-1031.35"
          },
          {
            "binary_name": "linux-riscv-5.11-headers-5.11.0-1031",
            "binary_version": "5.11.0-1031.35"
          },
          {
            "binary_name": "linux-riscv-5.11-tools-5.11.0-1031",
            "binary_version": "5.11.0-1031.35"
          },
          {
            "binary_name": "linux-tools-5.11.0-1031-generic",
            "binary_version": "5.11.0-1031.35"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-riscv-5.11",
        "purl": "pkg:deb/ubuntu/linux-riscv-5.11@5.11.0-1031.35?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.11.0-1015.16~20.04.1",
        "5.11.0-1017.18~20.04.1",
        "5.11.0-1018.19~20.04.2",
        "5.11.0-1020.21~20.04.1",
        "5.11.0-1021.22~20.04.1",
        "5.11.0-1022.23~20.04.1",
        "5.11.0-1023.24~20.04.1",
        "5.11.0-1024.25~20.04.1",
        "5.11.0-1026.28~20.04.1",
        "5.11.0-1028.31~20.04.1",
        "5.11.0-1029.32~20.04.1",
        "5.11.0-1030.34",
        "5.11.0-1031.35"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "block-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "crypto-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "fat-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "firewire-core-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "fs-core-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "fs-secondary-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "input-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "ipmi-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "kernel-image-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.8.0-29-generic",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "linux-headers-5.8.0-29-generic",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "linux-image-5.8.0-29-generic",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "linux-modules-5.8.0-29-generic",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.8.0-29-generic",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "linux-riscv-5.8-headers-5.8.0-29",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "linux-riscv-5.8-tools-5.8.0-29",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "linux-tools-5.8.0-29-generic",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "linux-udebs-generic",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "md-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "message-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "mouse-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "multipath-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "nfs-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "nic-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "nic-shared-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "nic-usb-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "parport-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "pata-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "plip-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "ppp-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "sata-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "scsi-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "storage-core-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "usb-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "virtio-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          },
          {
            "binary_name": "vlan-modules-5.8.0-29-generic-di",
            "binary_version": "5.8.0-29.31~20.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "linux-riscv-5.8",
        "purl": "pkg:deb/ubuntu/linux-riscv-5.8@5.8.0-29.31~20.04.1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.8.0-14.16~20.04.1",
        "5.8.0-14.16~20.04.3",
        "5.8.0-16.18~20.04.1",
        "5.8.0-17.19~20.04.1",
        "5.8.0-18.20~20.04.1",
        "5.8.0-20.22~20.04.1",
        "5.8.0-22.24~20.04.1",
        "5.8.0-25.27~20.04.1",
        "5.8.0-26.28~20.04.1",
        "5.8.0-29.31~20.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-127-generic",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-127-generic-64k",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-127-generic-lpae",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-127",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-127-generic",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-cloud-tools-common",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-headers-5.15.0-127",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-headers-5.15.0-127-generic",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-headers-5.15.0-127-generic-64k",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-headers-5.15.0-127-generic-lpae",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-image-5.15.0-127-generic",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-image-5.15.0-127-generic-lpae",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-127-generic",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-127-generic-64k",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-modules-5.15.0-127-generic",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-modules-5.15.0-127-generic-64k",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-modules-5.15.0-127-generic-lpae",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-127-generic",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-modules-iwlwifi-5.15.0-127-generic",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-source-5.15.0",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-tools-5.15.0-127",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-tools-5.15.0-127-generic",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-tools-5.15.0-127-generic-64k",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-tools-5.15.0-127-generic-lpae",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-tools-common",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-tools-host",
            "binary_version": "5.15.0-127.137"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux",
        "purl": "pkg:deb/ubuntu/linux@5.15.0-127.137?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-127.137"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.13.0-19.19",
        "5.15.0-17.17",
        "5.15.0-18.18",
        "5.15.0-22.22",
        "5.15.0-23.23",
        "5.15.0-25.25",
        "5.15.0-27.28",
        "5.15.0-30.31",
        "5.15.0-33.34",
        "5.15.0-35.36",
        "5.15.0-37.39",
        "5.15.0-39.42",
        "5.15.0-40.43",
        "5.15.0-41.44",
        "5.15.0-43.46",
        "5.15.0-46.49",
        "5.15.0-47.51",
        "5.15.0-48.54",
        "5.15.0-50.56",
        "5.15.0-52.58",
        "5.15.0-53.59",
        "5.15.0-56.62",
        "5.15.0-57.63",
        "5.15.0-58.64",
        "5.15.0-60.66",
        "5.15.0-67.74",
        "5.15.0-69.76",
        "5.15.0-70.77",
        "5.15.0-71.78",
        "5.15.0-72.79",
        "5.15.0-73.80",
        "5.15.0-75.82",
        "5.15.0-76.83",
        "5.15.0-78.85",
        "5.15.0-79.86",
        "5.15.0-82.91",
        "5.15.0-83.92",
        "5.15.0-84.93",
        "5.15.0-86.96",
        "5.15.0-87.97",
        "5.15.0-88.98",
        "5.15.0-89.99",
        "5.15.0-91.101",
        "5.15.0-92.102",
        "5.15.0-94.104",
        "5.15.0-97.107",
        "5.15.0-100.110",
        "5.15.0-101.111",
        "5.15.0-102.112",
        "5.15.0-105.115",
        "5.15.0-106.116",
        "5.15.0-107.117",
        "5.15.0-112.122",
        "5.15.0-113.123",
        "5.15.0-116.126",
        "5.15.0-117.127",
        "5.15.0-118.128",
        "5.15.0-119.129",
        "5.15.0-121.131",
        "5.15.0-122.132",
        "5.15.0-124.134",
        "5.15.0-125.135",
        "5.15.0-126.136"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-allwinner-5.19-headers-5.19.0-1015",
            "binary_version": "5.19.0-1015.15~22.04.1"
          },
          {
            "binary_name": "linux-allwinner-5.19-tools-5.19.0-1015",
            "binary_version": "5.19.0-1015.15~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.19.0-1015-allwinner",
            "binary_version": "5.19.0-1015.15~22.04.1"
          },
          {
            "binary_name": "linux-headers-5.19.0-1015-allwinner",
            "binary_version": "5.19.0-1015.15~22.04.1"
          },
          {
            "binary_name": "linux-image-5.19.0-1015-allwinner",
            "binary_version": "5.19.0-1015.15~22.04.1"
          },
          {
            "binary_name": "linux-modules-5.19.0-1015-allwinner",
            "binary_version": "5.19.0-1015.15~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.19.0-1015-allwinner",
            "binary_version": "5.19.0-1015.15~22.04.1"
          },
          {
            "binary_name": "linux-tools-5.19.0-1015-allwinner",
            "binary_version": "5.19.0-1015.15~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-allwinner-5.19",
        "purl": "pkg:deb/ubuntu/linux-allwinner-5.19@5.19.0-1015.15~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.19.0-1007.7~22.04.1",
        "5.19.0-1009.9~22.04.1",
        "5.19.0-1010.10~22.04.1",
        "5.19.0-1011.11~22.04.1",
        "5.19.0-1012.12~22.04.1",
        "5.19.0-1013.13~22.04.1",
        "5.19.0-1014.14~22.04.1",
        "5.19.0-1015.15~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-aws-cloud-tools-5.15.0-1073",
            "binary_version": "5.15.0-1073.79"
          },
          {
            "binary_name": "linux-aws-headers-5.15.0-1073",
            "binary_version": "5.15.0-1073.79"
          },
          {
            "binary_name": "linux-aws-tools-5.15.0-1073",
            "binary_version": "5.15.0-1073.79"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-1073-aws",
            "binary_version": "5.15.0-1073.79"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-1073-aws",
            "binary_version": "5.15.0-1073.79"
          },
          {
            "binary_name": "linux-headers-5.15.0-1073-aws",
            "binary_version": "5.15.0-1073.79"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1073-aws",
            "binary_version": "5.15.0-1073.79"
          },
          {
            "binary_name": "linux-modules-5.15.0-1073-aws",
            "binary_version": "5.15.0-1073.79"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1073-aws",
            "binary_version": "5.15.0-1073.79"
          },
          {
            "binary_name": "linux-tools-5.15.0-1073-aws",
            "binary_version": "5.15.0-1073.79"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-aws",
        "purl": "pkg:deb/ubuntu/linux-aws@5.15.0-1073.79?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1073.79"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.13.0-1005.6",
        "5.15.0-1002.4",
        "5.15.0-1003.5",
        "5.15.0-1004.6",
        "5.15.0-1005.7",
        "5.15.0-1008.10",
        "5.15.0-1009.11",
        "5.15.0-1011.14",
        "5.15.0-1013.17",
        "5.15.0-1014.18",
        "5.15.0-1015.19",
        "5.15.0-1017.21",
        "5.15.0-1019.23",
        "5.15.0-1020.24",
        "5.15.0-1021.25",
        "5.15.0-1022.26",
        "5.15.0-1023.27",
        "5.15.0-1026.30",
        "5.15.0-1027.31",
        "5.15.0-1028.32",
        "5.15.0-1030.34",
        "5.15.0-1031.35",
        "5.15.0-1033.37",
        "5.15.0-1034.38",
        "5.15.0-1035.39",
        "5.15.0-1036.40",
        "5.15.0-1037.41",
        "5.15.0-1038.43",
        "5.15.0-1039.44",
        "5.15.0-1040.45",
        "5.15.0-1042.47",
        "5.15.0-1043.48",
        "5.15.0-1044.49",
        "5.15.0-1045.50",
        "5.15.0-1047.52",
        "5.15.0-1048.53",
        "5.15.0-1049.54",
        "5.15.0-1050.55",
        "5.15.0-1051.56",
        "5.15.0-1052.57",
        "5.15.0-1053.58",
        "5.15.0-1055.60",
        "5.15.0-1056.61",
        "5.15.0-1057.63",
        "5.15.0-1060.66",
        "5.15.0-1061.67",
        "5.15.0-1062.68",
        "5.15.0-1063.69",
        "5.15.0-1064.70",
        "5.15.0-1065.71",
        "5.15.0-1066.72",
        "5.15.0-1067.73",
        "5.15.0-1068.74",
        "5.15.0-1069.75",
        "5.15.0-1070.76",
        "5.15.0-1071.77",
        "5.15.0-1072.78"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-aws-5.19-cloud-tools-5.19.0-1029",
            "binary_version": "5.19.0-1029.30~22.04.1"
          },
          {
            "binary_name": "linux-aws-5.19-headers-5.19.0-1029",
            "binary_version": "5.19.0-1029.30~22.04.1"
          },
          {
            "binary_name": "linux-aws-5.19-tools-5.19.0-1029",
            "binary_version": "5.19.0-1029.30~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-5.19.0-1029-aws",
            "binary_version": "5.19.0-1029.30~22.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-5.19.0-1029-aws",
            "binary_version": "5.19.0-1029.30~22.04.1"
          },
          {
            "binary_name": "linux-headers-5.19.0-1029-aws",
            "binary_version": "5.19.0-1029.30~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.19.0-1029-aws",
            "binary_version": "5.19.0-1029.30~22.04.1"
          },
          {
            "binary_name": "linux-modules-5.19.0-1029-aws",
            "binary_version": "5.19.0-1029.30~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.19.0-1029-aws",
            "binary_version": "5.19.0-1029.30~22.04.1"
          },
          {
            "binary_name": "linux-tools-5.19.0-1029-aws",
            "binary_version": "5.19.0-1029.30~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-aws-5.19",
        "purl": "pkg:deb/ubuntu/linux-aws-5.19@5.19.0-1029.30~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.19.0-1019.20~22.04.1",
        "5.19.0-1020.21~22.04.1",
        "5.19.0-1022.23~22.04.1",
        "5.19.0-1023.24~22.04.1",
        "5.19.0-1024.25~22.04.1",
        "5.19.0-1025.26~22.04.1",
        "5.19.0-1026.27~22.04.1",
        "5.19.0-1027.28~22.04.1",
        "5.19.0-1028.29~22.04.1",
        "5.19.0-1029.30~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-aws-6.2-cloud-tools-6.2.0-1018",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-aws-6.2-headers-6.2.0-1018",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-aws-6.2-tools-6.2.0-1018",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.2.0-1018-aws",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-6.2.0-1018-aws",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.2.0-1018-aws",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.2.0-1018-aws",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.2.0-1018-aws",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.2.0-1018-aws",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.2.0-1018-aws",
            "binary_version": "6.2.0-1018.18~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-aws-6.2",
        "purl": "pkg:deb/ubuntu/linux-aws-6.2@6.2.0-1018.18~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.2.0-1005.5~22.04.1",
        "6.2.0-1006.6~22.04.1",
        "6.2.0-1007.7~22.04.1",
        "6.2.0-1008.8~22.04.1",
        "6.2.0-1009.9~22.04.3",
        "6.2.0-1010.10~22.04.1",
        "6.2.0-1011.11~22.04.1",
        "6.2.0-1012.12~22.04.1",
        "6.2.0-1013.13~22.04.1",
        "6.2.0-1014.14~22.04.1",
        "6.2.0-1015.15~22.04.1",
        "6.2.0-1016.16~22.04.1",
        "6.2.0-1017.17~22.04.1",
        "6.2.0-1018.18~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-aws-6.5-cloud-tools-6.5.0-1024",
            "binary_version": "6.5.0-1024.24~22.04.1"
          },
          {
            "binary_name": "linux-aws-6.5-headers-6.5.0-1024",
            "binary_version": "6.5.0-1024.24~22.04.1"
          },
          {
            "binary_name": "linux-aws-6.5-tools-6.5.0-1024",
            "binary_version": "6.5.0-1024.24~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.5.0-1024-aws",
            "binary_version": "6.5.0-1024.24~22.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-6.5.0-1024-aws",
            "binary_version": "6.5.0-1024.24~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.5.0-1024-aws",
            "binary_version": "6.5.0-1024.24~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.5.0-1024-aws",
            "binary_version": "6.5.0-1024.24~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.5.0-1024-aws",
            "binary_version": "6.5.0-1024.24~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.5.0-1024-aws",
            "binary_version": "6.5.0-1024.24~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.5.0-1024-aws",
            "binary_version": "6.5.0-1024.24~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-aws-6.5",
        "purl": "pkg:deb/ubuntu/linux-aws-6.5@6.5.0-1024.24~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-1008.8~22.04.1",
        "6.5.0-1010.10~22.04.1",
        "6.5.0-1011.11~22.04.1",
        "6.5.0-1012.12~22.04.1",
        "6.5.0-1014.14~22.04.1",
        "6.5.0-1015.15~22.04.1",
        "6.5.0-1016.16~22.04.1",
        "6.5.0-1017.17~22.04.2",
        "6.5.0-1018.18~22.04.1",
        "6.5.0-1020.20~22.04.1",
        "6.5.0-1021.21~22.04.1",
        "6.5.0-1022.22~22.04.1",
        "6.5.0-1023.23~22.04.1",
        "6.5.0-1024.24~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-aws-6.8-cloud-tools-6.8.0-1027",
            "binary_version": "6.8.0-1027.29~22.04.1"
          },
          {
            "binary_name": "linux-aws-6.8-headers-6.8.0-1027",
            "binary_version": "6.8.0-1027.29~22.04.1"
          },
          {
            "binary_name": "linux-aws-6.8-tools-6.8.0-1027",
            "binary_version": "6.8.0-1027.29~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.8.0-1027-aws",
            "binary_version": "6.8.0-1027.29~22.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-6.8.0-1027-aws",
            "binary_version": "6.8.0-1027.29~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-1027-aws",
            "binary_version": "6.8.0-1027.29~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1027-aws",
            "binary_version": "6.8.0-1027.29~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-1027-aws",
            "binary_version": "6.8.0-1027.29~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1027-aws",
            "binary_version": "6.8.0-1027.29~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-1027-aws",
            "binary_version": "6.8.0-1027.29~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-aws-6.8",
        "purl": "pkg:deb/ubuntu/linux-aws-6.8@6.8.0-1027.29~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1027.29~22.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-1009.9~22.04.2",
        "6.8.0-1010.10~22.04.2",
        "6.8.0-1011.12~22.04.1",
        "6.8.0-1013.14~22.04.1",
        "6.8.0-1014.15~22.04.1",
        "6.8.0-1015.16~22.04.1",
        "6.8.0-1016.17~22.04.2",
        "6.8.0-1017.18~22.04.1",
        "6.8.0-1018.19~22.04.1",
        "6.8.0-1019.21~22.04.1",
        "6.8.0-1020.22~22.04.1",
        "6.8.0-1021.23~22.04.1",
        "6.8.0-1023.25~22.04.1",
        "6.8.0-1024.26~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-azure-cloud-tools-5.15.0-1078",
            "binary_version": "5.15.0-1078.87"
          },
          {
            "binary_name": "linux-azure-headers-5.15.0-1078",
            "binary_version": "5.15.0-1078.87"
          },
          {
            "binary_name": "linux-azure-tools-5.15.0-1078",
            "binary_version": "5.15.0-1078.87"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-1078-azure",
            "binary_version": "5.15.0-1078.87"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-1078-azure",
            "binary_version": "5.15.0-1078.87"
          },
          {
            "binary_name": "linux-headers-5.15.0-1078-azure",
            "binary_version": "5.15.0-1078.87"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1078-azure",
            "binary_version": "5.15.0-1078.87"
          },
          {
            "binary_name": "linux-modules-5.15.0-1078-azure",
            "binary_version": "5.15.0-1078.87"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1078-azure",
            "binary_version": "5.15.0-1078.87"
          },
          {
            "binary_name": "linux-modules-involflt-5.15.0-1078-azure",
            "binary_version": "5.15.0-1078.87"
          },
          {
            "binary_name": "linux-tools-5.15.0-1078-azure",
            "binary_version": "5.15.0-1078.87"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-azure",
        "purl": "pkg:deb/ubuntu/linux-azure@5.15.0-1078.87?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1078.87"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.13.0-1006.7",
        "5.15.0-1001.2",
        "5.15.0-1002.3",
        "5.15.0-1003.4",
        "5.15.0-1005.6",
        "5.15.0-1007.8",
        "5.15.0-1008.9",
        "5.15.0-1010.12",
        "5.15.0-1012.15",
        "5.15.0-1013.16",
        "5.15.0-1014.17",
        "5.15.0-1017.20",
        "5.15.0-1019.24",
        "5.15.0-1020.25",
        "5.15.0-1021.26",
        "5.15.0-1022.27",
        "5.15.0-1023.29",
        "5.15.0-1024.30",
        "5.15.0-1029.36",
        "5.15.0-1030.37",
        "5.15.0-1031.38",
        "5.15.0-1033.40",
        "5.15.0-1034.41",
        "5.15.0-1035.42",
        "5.15.0-1036.43",
        "5.15.0-1037.44",
        "5.15.0-1038.45",
        "5.15.0-1039.46",
        "5.15.0-1040.47",
        "5.15.0-1041.48",
        "5.15.0-1042.49",
        "5.15.0-1044.51",
        "5.15.0-1045.52",
        "5.15.0-1046.53",
        "5.15.0-1047.54",
        "5.15.0-1049.56",
        "5.15.0-1050.57",
        "5.15.0-1051.59",
        "5.15.0-1052.60",
        "5.15.0-1053.61",
        "5.15.0-1054.62",
        "5.15.0-1056.64",
        "5.15.0-1057.65",
        "5.15.0-1058.66",
        "5.15.0-1059.67",
        "5.15.0-1060.69",
        "5.15.0-1061.70",
        "5.15.0-1063.72",
        "5.15.0-1064.73",
        "5.15.0-1066.75",
        "5.15.0-1067.76",
        "5.15.0-1068.77",
        "5.15.0-1070.79",
        "5.15.0-1071.80",
        "5.15.0-1072.81",
        "5.15.0-1073.82",
        "5.15.0-1074.83",
        "5.15.0-1075.84"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-azure-5.19-cloud-tools-5.19.0-1027",
            "binary_version": "5.19.0-1027.30~22.04.2"
          },
          {
            "binary_name": "linux-azure-5.19-headers-5.19.0-1027",
            "binary_version": "5.19.0-1027.30~22.04.2"
          },
          {
            "binary_name": "linux-azure-5.19-tools-5.19.0-1027",
            "binary_version": "5.19.0-1027.30~22.04.2"
          },
          {
            "binary_name": "linux-buildinfo-5.19.0-1027-azure",
            "binary_version": "5.19.0-1027.30~22.04.2"
          },
          {
            "binary_name": "linux-cloud-tools-5.19.0-1027-azure",
            "binary_version": "5.19.0-1027.30~22.04.2"
          },
          {
            "binary_name": "linux-headers-5.19.0-1027-azure",
            "binary_version": "5.19.0-1027.30~22.04.2"
          },
          {
            "binary_name": "linux-image-unsigned-5.19.0-1027-azure",
            "binary_version": "5.19.0-1027.30~22.04.2"
          },
          {
            "binary_name": "linux-modules-5.19.0-1027-azure",
            "binary_version": "5.19.0-1027.30~22.04.2"
          },
          {
            "binary_name": "linux-modules-extra-5.19.0-1027-azure",
            "binary_version": "5.19.0-1027.30~22.04.2"
          },
          {
            "binary_name": "linux-tools-5.19.0-1027-azure",
            "binary_version": "5.19.0-1027.30~22.04.2"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-azure-5.19",
        "purl": "pkg:deb/ubuntu/linux-azure-5.19@5.19.0-1027.30~22.04.2?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.19.0-1020.21~22.04.1",
        "5.19.0-1021.22~22.04.1",
        "5.19.0-1022.23~22.04.1",
        "5.19.0-1023.24~22.04.1",
        "5.19.0-1025.28~22.04.1",
        "5.19.0-1026.29~22.04.1",
        "5.19.0-1027.30~22.04.2"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-azure-6.2-cloud-tools-6.2.0-1019",
            "binary_version": "6.2.0-1019.19~22.04.1"
          },
          {
            "binary_name": "linux-azure-6.2-headers-6.2.0-1019",
            "binary_version": "6.2.0-1019.19~22.04.1"
          },
          {
            "binary_name": "linux-azure-6.2-tools-6.2.0-1019",
            "binary_version": "6.2.0-1019.19~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.2.0-1019-azure",
            "binary_version": "6.2.0-1019.19~22.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-6.2.0-1019-azure",
            "binary_version": "6.2.0-1019.19~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.2.0-1019-azure",
            "binary_version": "6.2.0-1019.19~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.2.0-1019-azure",
            "binary_version": "6.2.0-1019.19~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.2.0-1019-azure",
            "binary_version": "6.2.0-1019.19~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.2.0-1019-azure",
            "binary_version": "6.2.0-1019.19~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.2.0-1019-azure",
            "binary_version": "6.2.0-1019.19~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-azure-6.2",
        "purl": "pkg:deb/ubuntu/linux-azure-6.2@6.2.0-1019.19~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.2.0-1005.5~22.04.1",
        "6.2.0-1006.6~22.04.1",
        "6.2.0-1007.7~22.04.1",
        "6.2.0-1008.8~22.04.1",
        "6.2.0-1009.9~22.04.3",
        "6.2.0-1011.11~22.04.1",
        "6.2.0-1012.12~22.04.1",
        "6.2.0-1014.14~22.04.1",
        "6.2.0-1015.15~22.04.1",
        "6.2.0-1016.16~22.04.1",
        "6.2.0-1017.17~22.04.1",
        "6.2.0-1018.18~22.04.1",
        "6.2.0-1019.19~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-azure-6.5-cloud-tools-6.5.0-1025",
            "binary_version": "6.5.0-1025.26~22.04.1"
          },
          {
            "binary_name": "linux-azure-6.5-headers-6.5.0-1025",
            "binary_version": "6.5.0-1025.26~22.04.1"
          },
          {
            "binary_name": "linux-azure-6.5-tools-6.5.0-1025",
            "binary_version": "6.5.0-1025.26~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.5.0-1025-azure",
            "binary_version": "6.5.0-1025.26~22.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-6.5.0-1025-azure",
            "binary_version": "6.5.0-1025.26~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.5.0-1025-azure",
            "binary_version": "6.5.0-1025.26~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.5.0-1025-azure",
            "binary_version": "6.5.0-1025.26~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.5.0-1025-azure",
            "binary_version": "6.5.0-1025.26~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.5.0-1025-azure",
            "binary_version": "6.5.0-1025.26~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.5.0-1025-azure",
            "binary_version": "6.5.0-1025.26~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-azure-6.5",
        "purl": "pkg:deb/ubuntu/linux-azure-6.5@6.5.0-1025.26~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-1007.7~22.04.1",
        "6.5.0-1009.9~22.04.1",
        "6.5.0-1010.10~22.04.1",
        "6.5.0-1011.11~22.04.1",
        "6.5.0-1015.15~22.04.1",
        "6.5.0-1016.16~22.04.1",
        "6.5.0-1017.17~22.04.1",
        "6.5.0-1018.19~22.04.2",
        "6.5.0-1019.20~22.04.1",
        "6.5.0-1021.22~22.04.1",
        "6.5.0-1022.23~22.04.1",
        "6.5.0-1023.24~22.04.1",
        "6.5.0-1024.25~22.04.1",
        "6.5.0-1025.26~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-azure-6.8-cloud-tools-6.8.0-1025",
            "binary_version": "6.8.0-1025.30~22.04.1"
          },
          {
            "binary_name": "linux-azure-6.8-headers-6.8.0-1025",
            "binary_version": "6.8.0-1025.30~22.04.1"
          },
          {
            "binary_name": "linux-azure-6.8-tools-6.8.0-1025",
            "binary_version": "6.8.0-1025.30~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.8.0-1025-azure",
            "binary_version": "6.8.0-1025.30~22.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-6.8.0-1025-azure",
            "binary_version": "6.8.0-1025.30~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-1025-azure",
            "binary_version": "6.8.0-1025.30~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1025-azure",
            "binary_version": "6.8.0-1025.30~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-1025-azure",
            "binary_version": "6.8.0-1025.30~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1025-azure",
            "binary_version": "6.8.0-1025.30~22.04.1"
          },
          {
            "binary_name": "linux-modules-involflt-6.8.0-1025-azure",
            "binary_version": "6.8.0-1025.30~22.04.1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.8.0-1025-azure",
            "binary_version": "6.8.0-1025.30~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-1025-azure",
            "binary_version": "6.8.0-1025.30~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-azure-6.8",
        "purl": "pkg:deb/ubuntu/linux-azure-6.8@6.8.0-1025.30~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1025.30~22.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-1008.8~22.04.1",
        "6.8.0-1009.9~22.04.1",
        "6.8.0-1010.10~22.04.1",
        "6.8.0-1012.14~22.04.1",
        "6.8.0-1013.15~22.04.1",
        "6.8.0-1014.16~22.04.1",
        "6.8.0-1015.17~22.04.2",
        "6.8.0-1017.20~22.04.1",
        "6.8.0-1018.21~22.04.1",
        "6.8.0-1020.23~22.04.1",
        "6.8.0-1021.25~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-azure-fde-cloud-tools-5.15.0-1120",
            "binary_version": "5.15.0-1120.129"
          },
          {
            "binary_name": "linux-azure-fde-headers-5.15.0-1120",
            "binary_version": "5.15.0-1120.129"
          },
          {
            "binary_name": "linux-azure-fde-tools-5.15.0-1120",
            "binary_version": "5.15.0-1120.129"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-1120-azure-fde",
            "binary_version": "5.15.0-1120.129"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-1120-azure-fde",
            "binary_version": "5.15.0-1120.129"
          },
          {
            "binary_name": "linux-headers-5.15.0-1120-azure-fde",
            "binary_version": "5.15.0-1120.129"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1120-azure-fde",
            "binary_version": "5.15.0-1120.129"
          },
          {
            "binary_name": "linux-modules-5.15.0-1120-azure-fde",
            "binary_version": "5.15.0-1120.129"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1120-azure-fde",
            "binary_version": "5.15.0-1120.129"
          },
          {
            "binary_name": "linux-modules-involflt-5.15.0-1120-azure-fde",
            "binary_version": "5.15.0-1120.129"
          },
          {
            "binary_name": "linux-tools-5.15.0-1120-azure-fde",
            "binary_version": "5.15.0-1120.129"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-azure-fde",
        "purl": "pkg:deb/ubuntu/linux-azure-fde@5.15.0-1120.129?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1019.24.1",
        "5.15.0-1024.30.1",
        "5.15.0-1029.36.1",
        "5.15.0-1030.37.1",
        "5.15.0-1031.38.1",
        "5.15.0-1033.40.1",
        "5.15.0-1034.41.1",
        "5.15.0-1035.42.1",
        "5.15.0-1036.43.1",
        "5.15.0-1037.44.1",
        "5.15.0-1038.45.1",
        "5.15.0-1039.46.1",
        "5.15.0-1041.48.1",
        "5.15.0-1042.49.1",
        "5.15.0-1044.51.1",
        "5.15.0-1045.52.1",
        "5.15.0-1046.53.1",
        "5.15.0-1047.54.1",
        "5.15.0-1049.56.1",
        "5.15.0-1050.57.1",
        "5.15.0-1051.59.1",
        "5.15.0-1052.60.1",
        "5.15.0-1053.61.1",
        "5.15.0-1054.62.1",
        "5.15.0-1056.64.1",
        "5.15.0-1057.65.1",
        "5.15.0-1058.66.1",
        "5.15.0-1059.67.1",
        "5.15.0-1060.69.1",
        "5.15.0-1061.70.1",
        "5.15.0-1063.72.1",
        "5.15.0-1064.73.1",
        "5.15.0-1065.74.1",
        "5.15.0-1067.76.1",
        "5.15.0-1068.77.1",
        "5.15.0-1070.79.1",
        "5.15.0-1071.80.1",
        "5.15.0-1072.81.1",
        "5.15.0-1073.82.1",
        "5.15.0-1076.85.1",
        "5.15.0-1078.87.1",
        "5.15.0-1081.90.1",
        "5.15.0-1082.91.1",
        "5.15.0-1084.93.1",
        "5.15.0-1086.95.1",
        "5.15.0-1087.96.1",
        "5.15.0-1088.97.1",
        "5.15.0-1089.98.1",
        "5.15.0-1090.99.1",
        "5.15.0-1091.100.1",
        "5.15.0-1092.101.1",
        "5.15.0-1094.103.1",
        "5.15.0-1095.104.1",
        "5.15.0-1096.105.1",
        "5.15.0-1097.106.1",
        "5.15.0-1098.107.1",
        "5.15.0-1102.111.1",
        "5.15.0-1109.118.1",
        "5.15.0-1110.119.1",
        "5.15.0-1111.120.1",
        "5.15.0-1114.123",
        "5.15.0-1116.125",
        "5.15.0-1117.126",
        "5.15.0-1118.127",
        "5.15.0-1119.128",
        "5.15.0-1120.129"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-unsigned-5.19.0-1027-azure-fde",
            "binary_version": "5.19.0-1027.30~22.04.2.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-azure-fde-5.19",
        "purl": "pkg:deb/ubuntu/linux-azure-fde-5.19@5.19.0-1027.30~22.04.2.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.19.0-1025.28~22.04.1.1",
        "5.19.0-1026.29~22.04.1.1",
        "5.19.0-1027.30~22.04.2.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-unsigned-6.2.0-1019-azure-fde",
            "binary_version": "6.2.0-1019.19~22.04.1.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-azure-fde-6.2",
        "purl": "pkg:deb/ubuntu/linux-azure-fde-6.2@6.2.0-1019.19~22.04.1.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.2.0-1008.8~22.04.1.1",
        "6.2.0-1009.9~22.04.3.1",
        "6.2.0-1011.11~22.04.1.1",
        "6.2.0-1012.12~22.04.1.1",
        "6.2.0-1014.14~22.04.1.1",
        "6.2.0-1015.15~22.04.1.1",
        "6.2.0-1016.16~22.04.1.1",
        "6.2.0-1017.17~22.04.1.1",
        "6.2.0-1018.18~22.04.1.1",
        "6.2.0-1019.19~22.04.1.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1072-gcp",
            "binary_version": "5.15.0-1072.80"
          },
          {
            "binary_name": "linux-gcp-headers-5.15.0-1072",
            "binary_version": "5.15.0-1072.80"
          },
          {
            "binary_name": "linux-gcp-tools-5.15.0-1072",
            "binary_version": "5.15.0-1072.80"
          },
          {
            "binary_name": "linux-headers-5.15.0-1072-gcp",
            "binary_version": "5.15.0-1072.80"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1072-gcp",
            "binary_version": "5.15.0-1072.80"
          },
          {
            "binary_name": "linux-modules-5.15.0-1072-gcp",
            "binary_version": "5.15.0-1072.80"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1072-gcp",
            "binary_version": "5.15.0-1072.80"
          },
          {
            "binary_name": "linux-tools-5.15.0-1072-gcp",
            "binary_version": "5.15.0-1072.80"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-gcp",
        "purl": "pkg:deb/ubuntu/linux-gcp@5.15.0-1072.80?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1072.80"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.13.0-1005.6",
        "5.15.0-1001.3",
        "5.15.0-1002.5",
        "5.15.0-1003.6",
        "5.15.0-1004.7",
        "5.15.0-1005.8",
        "5.15.0-1006.9",
        "5.15.0-1008.12",
        "5.15.0-1010.15",
        "5.15.0-1013.18",
        "5.15.0-1016.21",
        "5.15.0-1017.23",
        "5.15.0-1018.24",
        "5.15.0-1019.25",
        "5.15.0-1021.28",
        "5.15.0-1022.29",
        "5.15.0-1025.32",
        "5.15.0-1026.33",
        "5.15.0-1027.34",
        "5.15.0-1029.36",
        "5.15.0-1030.37",
        "5.15.0-1031.38",
        "5.15.0-1032.40",
        "5.15.0-1034.42",
        "5.15.0-1035.43",
        "5.15.0-1036.44",
        "5.15.0-1037.45",
        "5.15.0-1038.46",
        "5.15.0-1039.47",
        "5.15.0-1040.48",
        "5.15.0-1041.49",
        "5.15.0-1042.50",
        "5.15.0-1044.52",
        "5.15.0-1045.53",
        "5.15.0-1046.54",
        "5.15.0-1047.55",
        "5.15.0-1048.56",
        "5.15.0-1049.57",
        "5.15.0-1051.59",
        "5.15.0-1052.60",
        "5.15.0-1053.61",
        "5.15.0-1054.62",
        "5.15.0-1055.63",
        "5.15.0-1058.66",
        "5.15.0-1059.67",
        "5.15.0-1060.68",
        "5.15.0-1062.70",
        "5.15.0-1063.71",
        "5.15.0-1064.72",
        "5.15.0-1065.73",
        "5.15.0-1066.74",
        "5.15.0-1067.75",
        "5.15.0-1068.76",
        "5.15.0-1069.77",
        "5.15.0-1070.78",
        "5.15.0-1071.79"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.19.0-1030-gcp",
            "binary_version": "5.19.0-1030.32~22.04.1"
          },
          {
            "binary_name": "linux-gcp-5.19-headers-5.19.0-1030",
            "binary_version": "5.19.0-1030.32~22.04.1"
          },
          {
            "binary_name": "linux-gcp-5.19-tools-5.19.0-1030",
            "binary_version": "5.19.0-1030.32~22.04.1"
          },
          {
            "binary_name": "linux-headers-5.19.0-1030-gcp",
            "binary_version": "5.19.0-1030.32~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-5.19.0-1030-gcp",
            "binary_version": "5.19.0-1030.32~22.04.1"
          },
          {
            "binary_name": "linux-modules-5.19.0-1030-gcp",
            "binary_version": "5.19.0-1030.32~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.19.0-1030-gcp",
            "binary_version": "5.19.0-1030.32~22.04.1"
          },
          {
            "binary_name": "linux-tools-5.19.0-1030-gcp",
            "binary_version": "5.19.0-1030.32~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-gcp-5.19",
        "purl": "pkg:deb/ubuntu/linux-gcp-5.19@5.19.0-1030.32~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.19.0-1020.22~22.04.2",
        "5.19.0-1021.23~22.04.1",
        "5.19.0-1022.24~22.04.1",
        "5.19.0-1024.26~22.04.1",
        "5.19.0-1025.27~22.04.1",
        "5.19.0-1026.28~22.04.1",
        "5.19.0-1027.29~22.04.1",
        "5.19.0-1030.32~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.2.0-1021-gcp",
            "binary_version": "6.2.0-1021.23~22.04.1"
          },
          {
            "binary_name": "linux-gcp-6.2-headers-6.2.0-1021",
            "binary_version": "6.2.0-1021.23~22.04.1"
          },
          {
            "binary_name": "linux-gcp-6.2-tools-6.2.0-1021",
            "binary_version": "6.2.0-1021.23~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.2.0-1021-gcp",
            "binary_version": "6.2.0-1021.23~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.2.0-1021-gcp",
            "binary_version": "6.2.0-1021.23~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.2.0-1021-gcp",
            "binary_version": "6.2.0-1021.23~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.2.0-1021-gcp",
            "binary_version": "6.2.0-1021.23~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.2.0-1021-gcp",
            "binary_version": "6.2.0-1021.23~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-gcp-6.2",
        "purl": "pkg:deb/ubuntu/linux-gcp-6.2@6.2.0-1021.23~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.2.0-1009.9~22.04.3",
        "6.2.0-1010.10~22.04.1",
        "6.2.0-1011.11~22.04.1",
        "6.2.0-1011.11~22.04.3",
        "6.2.0-1012.12~22.04.1",
        "6.2.0-1013.13~22.04.1",
        "6.2.0-1014.14~22.04.1",
        "6.2.0-1016.18~22.04.1",
        "6.2.0-1017.19~22.04.1",
        "6.2.0-1018.20~22.04.1",
        "6.2.0-1019.21~22.04.1",
        "6.2.0-1021.23~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.5.0-1025-gcp",
            "binary_version": "6.5.0-1025.27~22.04.1"
          },
          {
            "binary_name": "linux-gcp-6.5-headers-6.5.0-1025",
            "binary_version": "6.5.0-1025.27~22.04.1"
          },
          {
            "binary_name": "linux-gcp-6.5-tools-6.5.0-1025",
            "binary_version": "6.5.0-1025.27~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.5.0-1025-gcp",
            "binary_version": "6.5.0-1025.27~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.5.0-1025-gcp",
            "binary_version": "6.5.0-1025.27~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.5.0-1025-gcp",
            "binary_version": "6.5.0-1025.27~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.5.0-1025-gcp",
            "binary_version": "6.5.0-1025.27~22.04.1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.5.0-1025-gcp",
            "binary_version": "6.5.0-1025.27~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.5.0-1025-gcp",
            "binary_version": "6.5.0-1025.27~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-gcp-6.5",
        "purl": "pkg:deb/ubuntu/linux-gcp-6.5@6.5.0-1025.27~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-1010.10~22.04.3",
        "6.5.0-1011.11~22.04.1",
        "6.5.0-1013.13~22.04.1",
        "6.5.0-1014.14~22.04.1",
        "6.5.0-1015.15~22.04.1",
        "6.5.0-1016.16~22.04.1",
        "6.5.0-1017.17~22.04.1",
        "6.5.0-1018.18~22.04.1",
        "6.5.0-1020.20~22.04.1",
        "6.5.0-1022.24~22.04.1",
        "6.5.0-1023.25~22.04.1",
        "6.5.0-1024.26~22.04.1",
        "6.5.0-1025.27~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-1026-gcp",
            "binary_version": "6.8.0-1026.28~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.8.0-1026-gcp-64k",
            "binary_version": "6.8.0-1026.28~22.04.1"
          },
          {
            "binary_name": "linux-gcp-6.8-headers-6.8.0-1026",
            "binary_version": "6.8.0-1026.28~22.04.1"
          },
          {
            "binary_name": "linux-gcp-6.8-tools-6.8.0-1026",
            "binary_version": "6.8.0-1026.28~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-1026-gcp",
            "binary_version": "6.8.0-1026.28~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-1026-gcp-64k",
            "binary_version": "6.8.0-1026.28~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1026-gcp",
            "binary_version": "6.8.0-1026.28~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1026-gcp-64k",
            "binary_version": "6.8.0-1026.28~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-1026-gcp",
            "binary_version": "6.8.0-1026.28~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-1026-gcp-64k",
            "binary_version": "6.8.0-1026.28~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1026-gcp",
            "binary_version": "6.8.0-1026.28~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1026-gcp-64k",
            "binary_version": "6.8.0-1026.28~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-1026-gcp",
            "binary_version": "6.8.0-1026.28~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-1026-gcp-64k",
            "binary_version": "6.8.0-1026.28~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-gcp-6.8",
        "purl": "pkg:deb/ubuntu/linux-gcp-6.8@6.8.0-1026.28~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1026.28~22.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-1010.11~22.04.1",
        "6.8.0-1011.12~22.04.1",
        "6.8.0-1012.13~22.04.1",
        "6.8.0-1013.14~22.04.1",
        "6.8.0-1014.16~22.04.1",
        "6.8.0-1015.17~22.04.1",
        "6.8.0-1016.18~22.04.1",
        "6.8.0-1017.19~22.04.1",
        "6.8.0-1018.20~22.04.1",
        "6.8.0-1019.21~22.04.1",
        "6.8.0-1020.22~22.04.1",
        "6.8.0-1021.23~22.04.1",
        "6.8.0-1024.26~22.04.1",
        "6.8.0-1025.27~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1070-gke",
            "binary_version": "5.15.0-1070.76"
          },
          {
            "binary_name": "linux-gke-headers-5.15.0-1070",
            "binary_version": "5.15.0-1070.76"
          },
          {
            "binary_name": "linux-gke-tools-5.15.0-1070",
            "binary_version": "5.15.0-1070.76"
          },
          {
            "binary_name": "linux-headers-5.15.0-1070-gke",
            "binary_version": "5.15.0-1070.76"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1070-gke",
            "binary_version": "5.15.0-1070.76"
          },
          {
            "binary_name": "linux-modules-5.15.0-1070-gke",
            "binary_version": "5.15.0-1070.76"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1070-gke",
            "binary_version": "5.15.0-1070.76"
          },
          {
            "binary_name": "linux-tools-5.15.0-1070-gke",
            "binary_version": "5.15.0-1070.76"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-gke",
        "purl": "pkg:deb/ubuntu/linux-gke@5.15.0-1070.76?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1070.76"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1002.2",
        "5.15.0-1003.3",
        "5.15.0-1004.5",
        "5.15.0-1005.6",
        "5.15.0-1006.7",
        "5.15.0-1008.10",
        "5.15.0-1010.13",
        "5.15.0-1011.14",
        "5.15.0-1014.17",
        "5.15.0-1015.18",
        "5.15.0-1016.19",
        "5.15.0-1017.20",
        "5.15.0-1019.23",
        "5.15.0-1020.25",
        "5.15.0-1023.28",
        "5.15.0-1024.29",
        "5.15.0-1027.32",
        "5.15.0-1028.33",
        "5.15.0-1030.35",
        "5.15.0-1031.36",
        "5.15.0-1032.37",
        "5.15.0-1033.38",
        "5.15.0-1034.39",
        "5.15.0-1035.40",
        "5.15.0-1036.41",
        "5.15.0-1037.42",
        "5.15.0-1038.43",
        "5.15.0-1039.44",
        "5.15.0-1040.45",
        "5.15.0-1041.46",
        "5.15.0-1042.47",
        "5.15.0-1044.49",
        "5.15.0-1045.50",
        "5.15.0-1046.51",
        "5.15.0-1047.52",
        "5.15.0-1048.53",
        "5.15.0-1049.54",
        "5.15.0-1050.55",
        "5.15.0-1051.56",
        "5.15.0-1052.57",
        "5.15.0-1053.58",
        "5.15.0-1054.59",
        "5.15.0-1057.62",
        "5.15.0-1058.63",
        "5.15.0-1059.64",
        "5.15.0-1060.66",
        "5.15.0-1061.67",
        "5.15.0-1062.68",
        "5.15.0-1063.69",
        "5.15.0-1064.70",
        "5.15.0-1065.71",
        "5.15.0-1066.72",
        "5.15.0-1067.73",
        "5.15.0-1068.74",
        "5.15.0-1069.75"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1056-gkeop",
            "binary_version": "5.15.0-1056.63"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-1056-gkeop",
            "binary_version": "5.15.0-1056.63"
          },
          {
            "binary_name": "linux-gkeop-cloud-tools-5.15.0-1056",
            "binary_version": "5.15.0-1056.63"
          },
          {
            "binary_name": "linux-gkeop-headers-5.15.0-1056",
            "binary_version": "5.15.0-1056.63"
          },
          {
            "binary_name": "linux-gkeop-tools-5.15.0-1056",
            "binary_version": "5.15.0-1056.63"
          },
          {
            "binary_name": "linux-headers-5.15.0-1056-gkeop",
            "binary_version": "5.15.0-1056.63"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1056-gkeop",
            "binary_version": "5.15.0-1056.63"
          },
          {
            "binary_name": "linux-modules-5.15.0-1056-gkeop",
            "binary_version": "5.15.0-1056.63"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1056-gkeop",
            "binary_version": "5.15.0-1056.63"
          },
          {
            "binary_name": "linux-tools-5.15.0-1056-gkeop",
            "binary_version": "5.15.0-1056.63"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-gkeop",
        "purl": "pkg:deb/ubuntu/linux-gkeop@5.15.0-1056.63?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1056.63"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1001.2",
        "5.15.0-1002.4",
        "5.15.0-1003.5",
        "5.15.0-1004.6",
        "5.15.0-1005.7",
        "5.15.0-1007.10",
        "5.15.0-1008.12",
        "5.15.0-1011.15",
        "5.15.0-1012.16",
        "5.15.0-1013.17",
        "5.15.0-1015.19",
        "5.15.0-1016.21",
        "5.15.0-1017.22",
        "5.15.0-1018.23",
        "5.15.0-1019.24",
        "5.15.0-1020.25",
        "5.15.0-1021.26",
        "5.15.0-1022.27",
        "5.15.0-1023.28",
        "5.15.0-1024.29",
        "5.15.0-1025.30",
        "5.15.0-1026.31",
        "5.15.0-1027.32",
        "5.15.0-1028.33",
        "5.15.0-1030.35",
        "5.15.0-1031.37",
        "5.15.0-1032.38",
        "5.15.0-1033.39",
        "5.15.0-1034.40",
        "5.15.0-1035.41",
        "5.15.0-1036.42",
        "5.15.0-1037.43",
        "5.15.0-1038.44",
        "5.15.0-1039.45",
        "5.15.0-1040.46",
        "5.15.0-1043.50",
        "5.15.0-1044.51",
        "5.15.0-1045.52",
        "5.15.0-1046.53",
        "5.15.0-1047.54",
        "5.15.0-1048.55",
        "5.15.0-1049.56",
        "5.15.0-1050.57",
        "5.15.0-1051.58",
        "5.15.0-1052.59",
        "5.15.0-1053.60",
        "5.15.0-1054.61",
        "5.15.0-1055.62"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.19.0-50-generic",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-buildinfo-5.19.0-50-generic-64k",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-buildinfo-5.19.0-50-generic-lpae",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-cloud-tools-5.19.0-50-generic",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-headers-5.19.0-50-generic",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-headers-5.19.0-50-generic-64k",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-headers-5.19.0-50-generic-lpae",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-hwe-5.19-cloud-tools-5.19.0-50",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-hwe-5.19-cloud-tools-common",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-hwe-5.19-headers-5.19.0-50",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-hwe-5.19-tools-5.19.0-50",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-hwe-5.19-tools-common",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-hwe-5.19-tools-host",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-image-5.19.0-50-generic",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-image-5.19.0-50-generic-lpae",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-image-unsigned-5.19.0-50-generic",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-image-unsigned-5.19.0-50-generic-64k",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-modules-5.19.0-50-generic",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-modules-5.19.0-50-generic-64k",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-modules-5.19.0-50-generic-lpae",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-modules-extra-5.19.0-50-generic",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-modules-ipu6-5.19.0-50-generic",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-modules-ivsc-5.19.0-50-generic",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-modules-iwlwifi-5.19.0-50-generic",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-source-5.19.0",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-tools-5.19.0-50-generic",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-tools-5.19.0-50-generic-64k",
            "binary_version": "5.19.0-50.50"
          },
          {
            "binary_name": "linux-tools-5.19.0-50-generic-lpae",
            "binary_version": "5.19.0-50.50"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-hwe-5.19",
        "purl": "pkg:deb/ubuntu/linux-hwe-5.19@5.19.0-50.50?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.19.0-28.29~22.04.1",
        "5.19.0-32.33~22.04.1",
        "5.19.0-35.36~22.04.1",
        "5.19.0-38.39~22.04.1",
        "5.19.0-40.41~22.04.1",
        "5.19.0-41.42~22.04.1",
        "5.19.0-42.43~22.04.1",
        "5.19.0-43.44~22.04.1",
        "5.19.0-45.46~22.04.1",
        "5.19.0-46.47~22.04.1",
        "5.19.0-50.50"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.2.0-39-generic",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.2.0-39-generic-64k",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.2.0-39-generic-lpae",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-6.2.0-39-generic",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.2.0-39-generic",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.2.0-39-generic-64k",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.2.0-39-generic-lpae",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-hwe-6.2-cloud-tools-6.2.0-39",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-hwe-6.2-cloud-tools-common",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-hwe-6.2-headers-6.2.0-39",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-hwe-6.2-tools-6.2.0-39",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-hwe-6.2-tools-common",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-hwe-6.2-tools-host",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-image-6.2.0-39-generic",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-image-6.2.0-39-generic-lpae",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.2.0-39-generic",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.2.0-39-generic-64k",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.2.0-39-generic",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.2.0-39-generic-64k",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.2.0-39-generic-lpae",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.2.0-39-generic",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-modules-ipu6-6.2.0-39-generic",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-modules-ivsc-6.2.0-39-generic",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.2.0-39-generic",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-source-6.2.0",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.2.0-39-generic",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.2.0-39-generic-64k",
            "binary_version": "6.2.0-39.40~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.2.0-39-generic-lpae",
            "binary_version": "6.2.0-39.40~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-hwe-6.2",
        "purl": "pkg:deb/ubuntu/linux-hwe-6.2@6.2.0-39.40~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.2.0-25.25~22.04.2",
        "6.2.0-26.26~22.04.1",
        "6.2.0-31.31~22.04.1",
        "6.2.0-32.32~22.04.1",
        "6.2.0-33.33~22.04.1",
        "6.2.0-34.34~22.04.1",
        "6.2.0-35.35~22.04.1",
        "6.2.0-36.37~22.04.1",
        "6.2.0-37.38~22.04.1",
        "6.2.0-39.40~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.5.0-45-generic",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.5.0-45-generic-64k",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-6.5.0-45-generic",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.5.0-45-generic",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.5.0-45-generic-64k",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-hwe-6.5-cloud-tools-6.5.0-45",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-hwe-6.5-cloud-tools-common",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-hwe-6.5-headers-6.5.0-45",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-hwe-6.5-tools-6.5.0-45",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-hwe-6.5-tools-common",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-hwe-6.5-tools-host",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-image-6.5.0-45-generic",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.5.0-45-generic",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.5.0-45-generic-64k",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.5.0-45-generic",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.5.0-45-generic-64k",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.5.0-45-generic",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-modules-ipu6-6.5.0-45-generic",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-modules-ivsc-6.5.0-45-generic",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.5.0-45-generic",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-source-6.5.0",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.5.0-45-generic",
            "binary_version": "6.5.0-45.45~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.5.0-45-generic-64k",
            "binary_version": "6.5.0-45.45~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-hwe-6.5",
        "purl": "pkg:deb/ubuntu/linux-hwe-6.5@6.5.0-45.45~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-14.14~22.04.1",
        "6.5.0-15.15~22.04.1",
        "6.5.0-17.17~22.04.1",
        "6.5.0-18.18~22.04.1",
        "6.5.0-21.21~22.04.1",
        "6.5.0-25.25~22.04.1",
        "6.5.0-26.26~22.04.1",
        "6.5.0-27.28~22.04.1",
        "6.5.0-28.29~22.04.1",
        "6.5.0-35.35~22.04.1",
        "6.5.0-41.41~22.04.2",
        "6.5.0-44.44~22.04.1",
        "6.5.0-45.45~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-57-generic",
            "binary_version": "6.8.0-57.59~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.8.0-57-generic-64k",
            "binary_version": "6.8.0-57.59~22.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-6.8.0-57-generic",
            "binary_version": "6.8.0-57.59~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-57-generic",
            "binary_version": "6.8.0-57.59~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-57-generic-64k",
            "binary_version": "6.8.0-57.59~22.04.1"
          },
          {
            "binary_name": "linux-hwe-6.8-cloud-tools-6.8.0-57",
            "binary_version": "6.8.0-57.59~22.04.1"
          },
          {
            "binary_name": "linux-hwe-6.8-headers-6.8.0-57",
            "binary_version": "6.8.0-57.59~22.04.1"
          },
          {
            "binary_name": "linux-hwe-6.8-tools-6.8.0-57",
            "binary_version": "6.8.0-57.59~22.04.1"
          },
          {
            "binary_name": "linux-image-6.8.0-57-generic",
            "binary_version": "6.8.0-57.59~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-57-generic",
            "binary_version": "6.8.0-57.59~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-57-generic-64k",
            "binary_version": "6.8.0-57.59~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-57-generic",
            "binary_version": "6.8.0-57.59~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-57-generic-64k",
            "binary_version": "6.8.0-57.59~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-57-generic",
            "binary_version": "6.8.0-57.59~22.04.1"
          },
          {
            "binary_name": "linux-modules-ipu6-6.8.0-57-generic",
            "binary_version": "6.8.0-57.59~22.04.1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.8.0-57-generic",
            "binary_version": "6.8.0-57.59~22.04.1"
          },
          {
            "binary_name": "linux-modules-usbio-6.8.0-57-generic",
            "binary_version": "6.8.0-57.59~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-57-generic",
            "binary_version": "6.8.0-57.59~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-57-generic-64k",
            "binary_version": "6.8.0-57.59~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-hwe-6.8",
        "purl": "pkg:deb/ubuntu/linux-hwe-6.8@6.8.0-57.59~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-57.59~22.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-38.38~22.04.1",
        "6.8.0-39.39~22.04.1",
        "6.8.0-40.40~22.04.3",
        "6.8.0-45.45~22.04.1",
        "6.8.0-47.47~22.04.1",
        "6.8.0-48.48~22.04.1",
        "6.8.0-49.49~22.04.1",
        "6.8.0-50.51~22.04.1",
        "6.8.0-51.52~22.04.1",
        "6.8.0-52.53~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1066-ibm",
            "binary_version": "5.15.0-1066.69"
          },
          {
            "binary_name": "linux-headers-5.15.0-1066-ibm",
            "binary_version": "5.15.0-1066.69"
          },
          {
            "binary_name": "linux-ibm-cloud-tools-common",
            "binary_version": "5.15.0-1066.69"
          },
          {
            "binary_name": "linux-ibm-headers-5.15.0-1066",
            "binary_version": "5.15.0-1066.69"
          },
          {
            "binary_name": "linux-ibm-source-5.15.0",
            "binary_version": "5.15.0-1066.69"
          },
          {
            "binary_name": "linux-ibm-tools-5.15.0-1066",
            "binary_version": "5.15.0-1066.69"
          },
          {
            "binary_name": "linux-ibm-tools-common",
            "binary_version": "5.15.0-1066.69"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1066-ibm",
            "binary_version": "5.15.0-1066.69"
          },
          {
            "binary_name": "linux-modules-5.15.0-1066-ibm",
            "binary_version": "5.15.0-1066.69"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1066-ibm",
            "binary_version": "5.15.0-1066.69"
          },
          {
            "binary_name": "linux-tools-5.15.0-1066-ibm",
            "binary_version": "5.15.0-1066.69"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-ibm",
        "purl": "pkg:deb/ubuntu/linux-ibm@5.15.0-1066.69?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1066.69"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1002.2",
        "5.15.0-1003.3",
        "5.15.0-1004.4",
        "5.15.0-1005.5",
        "5.15.0-1007.8",
        "5.15.0-1009.11",
        "5.15.0-1010.12",
        "5.15.0-1012.14",
        "5.15.0-1013.15",
        "5.15.0-1015.17",
        "5.15.0-1017.20",
        "5.15.0-1018.21",
        "5.15.0-1021.24",
        "5.15.0-1022.25",
        "5.15.0-1023.26",
        "5.15.0-1025.28",
        "5.15.0-1026.29",
        "5.15.0-1027.30",
        "5.15.0-1028.31",
        "5.15.0-1029.32",
        "5.15.0-1030.33",
        "5.15.0-1031.34",
        "5.15.0-1032.35",
        "5.15.0-1033.36",
        "5.15.0-1034.37",
        "5.15.0-1035.38",
        "5.15.0-1036.39",
        "5.15.0-1037.40",
        "5.15.0-1038.41",
        "5.15.0-1040.43",
        "5.15.0-1041.44",
        "5.15.0-1042.45",
        "5.15.0-1043.46",
        "5.15.0-1044.47",
        "5.15.0-1045.48",
        "5.15.0-1046.49",
        "5.15.0-1047.50",
        "5.15.0-1048.51",
        "5.15.0-1049.52",
        "5.15.0-1050.53",
        "5.15.0-1053.56",
        "5.15.0-1054.57",
        "5.15.0-1055.58",
        "5.15.0-1056.59",
        "5.15.0-1057.60",
        "5.15.0-1058.61",
        "5.15.0-1059.62",
        "5.15.0-1060.63",
        "5.15.0-1061.64",
        "5.15.0-1062.65",
        "5.15.0-1063.66",
        "5.15.0-1064.67",
        "5.15.0-1065.68"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-1023-ibm",
            "binary_version": "6.8.0-1023.23~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-1023-ibm",
            "binary_version": "6.8.0-1023.23~22.04.1"
          },
          {
            "binary_name": "linux-ibm-6.8-headers-6.8.0-1023",
            "binary_version": "6.8.0-1023.23~22.04.1"
          },
          {
            "binary_name": "linux-ibm-6.8-tools-6.8.0-1023",
            "binary_version": "6.8.0-1023.23~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1023-ibm",
            "binary_version": "6.8.0-1023.23~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-1023-ibm",
            "binary_version": "6.8.0-1023.23~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1023-ibm",
            "binary_version": "6.8.0-1023.23~22.04.1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.8.0-1023-ibm",
            "binary_version": "6.8.0-1023.23~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-1023-ibm",
            "binary_version": "6.8.0-1023.23~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-ibm-6.8",
        "purl": "pkg:deb/ubuntu/linux-ibm-6.8@6.8.0-1023.23~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1023.23~22.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-1008.8~22.04.1",
        "6.8.0-1010.10~22.04.1",
        "6.8.0-1011.11~22.04.1",
        "6.8.0-1012.12~22.04.1",
        "6.8.0-1013.13~22.04.1",
        "6.8.0-1014.14~22.04.1",
        "6.8.0-1015.15~22.04.1",
        "6.8.0-1016.16~22.04.1",
        "6.8.0-1017.17~22.04.1",
        "6.8.0-1018.18~22.04.1",
        "6.8.0-1019.19~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1071-intel-iotg",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-1071-intel-iotg",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-headers-5.15.0-1071-intel-iotg",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1071-intel-iotg",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-intel-iotg-cloud-tools-5.15.0-1071",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-intel-iotg-cloud-tools-common",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-intel-iotg-headers-5.15.0-1071",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-intel-iotg-tools-5.15.0-1071",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-intel-iotg-tools-common",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-intel-iotg-tools-host",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-modules-5.15.0-1071-intel-iotg",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1071-intel-iotg",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-modules-iwlwifi-5.15.0-1071-intel-iotg",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-tools-5.15.0-1071-intel-iotg",
            "binary_version": "5.15.0-1071.77"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-intel-iotg",
        "purl": "pkg:deb/ubuntu/linux-intel-iotg@5.15.0-1071.77?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1071.77"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1004.6",
        "5.15.0-1008.11",
        "5.15.0-1010.14",
        "5.15.0-1013.17",
        "5.15.0-1015.20",
        "5.15.0-1016.21",
        "5.15.0-1017.22",
        "5.15.0-1018.23",
        "5.15.0-1021.26",
        "5.15.0-1023.28",
        "5.15.0-1025.30",
        "5.15.0-1026.31",
        "5.15.0-1027.32",
        "5.15.0-1028.33",
        "5.15.0-1030.35",
        "5.15.0-1031.36",
        "5.15.0-1033.38",
        "5.15.0-1034.39",
        "5.15.0-1035.40",
        "5.15.0-1036.41",
        "5.15.0-1037.42",
        "5.15.0-1038.43",
        "5.15.0-1039.45",
        "5.15.0-1040.46",
        "5.15.0-1043.49",
        "5.15.0-1045.51",
        "5.15.0-1046.52",
        "5.15.0-1047.53",
        "5.15.0-1048.54",
        "5.15.0-1049.55",
        "5.15.0-1050.56",
        "5.15.0-1051.57",
        "5.15.0-1052.58",
        "5.15.0-1055.61",
        "5.15.0-1057.63",
        "5.15.0-1058.64",
        "5.15.0-1059.65",
        "5.15.0-1060.66",
        "5.15.0-1061.67",
        "5.15.0-1062.68",
        "5.15.0-1063.69",
        "5.15.0-1064.70",
        "5.15.0-1065.71",
        "5.15.0-1066.72",
        "5.15.0-1067.73"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1070-kvm",
            "binary_version": "5.15.0-1070.75"
          },
          {
            "binary_name": "linux-headers-5.15.0-1070-kvm",
            "binary_version": "5.15.0-1070.75"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1070-kvm",
            "binary_version": "5.15.0-1070.75"
          },
          {
            "binary_name": "linux-kvm-headers-5.15.0-1070",
            "binary_version": "5.15.0-1070.75"
          },
          {
            "binary_name": "linux-kvm-tools-5.15.0-1070",
            "binary_version": "5.15.0-1070.75"
          },
          {
            "binary_name": "linux-modules-5.15.0-1070-kvm",
            "binary_version": "5.15.0-1070.75"
          },
          {
            "binary_name": "linux-tools-5.15.0-1070-kvm",
            "binary_version": "5.15.0-1070.75"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-kvm",
        "purl": "pkg:deb/ubuntu/linux-kvm@5.15.0-1070.75?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1070.75"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.13.0-1004.4",
        "5.13.0-1006.6+22.04.1",
        "5.13.0-1007.7+22.04.1",
        "5.13.0-1010.11+22.04.1",
        "5.15.0-1002.2",
        "5.15.0-1004.4",
        "5.15.0-1005.5",
        "5.15.0-1007.7",
        "5.15.0-1008.8",
        "5.15.0-1010.11",
        "5.15.0-1012.14",
        "5.15.0-1013.16",
        "5.15.0-1016.19",
        "5.15.0-1017.21",
        "5.15.0-1018.22",
        "5.15.0-1019.23",
        "5.15.0-1020.24",
        "5.15.0-1021.26",
        "5.15.0-1024.29",
        "5.15.0-1025.30",
        "5.15.0-1026.31",
        "5.15.0-1028.33",
        "5.15.0-1029.34",
        "5.15.0-1030.35",
        "5.15.0-1031.36",
        "5.15.0-1032.37",
        "5.15.0-1033.38",
        "5.15.0-1034.39",
        "5.15.0-1035.40",
        "5.15.0-1037.42",
        "5.15.0-1038.43",
        "5.15.0-1039.44",
        "5.15.0-1040.45",
        "5.15.0-1041.46",
        "5.15.0-1042.47",
        "5.15.0-1044.49",
        "5.15.0-1045.50",
        "5.15.0-1046.51",
        "5.15.0-1047.52",
        "5.15.0-1048.53",
        "5.15.0-1049.54",
        "5.15.0-1050.55",
        "5.15.0-1051.56",
        "5.15.0-1052.57",
        "5.15.0-1053.58",
        "5.15.0-1054.59",
        "5.15.0-1057.62",
        "5.15.0-1058.63",
        "5.15.0-1059.64",
        "5.15.0-1060.65",
        "5.15.0-1061.66",
        "5.15.0-1062.67",
        "5.15.0-1063.68",
        "5.15.0-1064.69",
        "5.15.0-1065.70",
        "5.15.0-1066.71",
        "5.15.0-1067.72",
        "5.15.0-1068.73",
        "5.15.0-1069.74"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-127-lowlatency",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-127-lowlatency-64k",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-127-lowlatency",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-headers-5.15.0-127-lowlatency",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-headers-5.15.0-127-lowlatency-64k",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-127-lowlatency",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-127-lowlatency-64k",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-lowlatency-cloud-tools-5.15.0-127",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-lowlatency-headers-5.15.0-127",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-lowlatency-tools-5.15.0-127",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-modules-5.15.0-127-lowlatency",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-modules-5.15.0-127-lowlatency-64k",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-modules-iwlwifi-5.15.0-127-lowlatency",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-tools-5.15.0-127-lowlatency",
            "binary_version": "5.15.0-127.137"
          },
          {
            "binary_name": "linux-tools-5.15.0-127-lowlatency-64k",
            "binary_version": "5.15.0-127.137"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-lowlatency",
        "purl": "pkg:deb/ubuntu/linux-lowlatency@5.15.0-127.137?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-127.137"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-22.22",
        "5.15.0-23.23",
        "5.15.0-24.24",
        "5.15.0-27.28",
        "5.15.0-30.31",
        "5.15.0-33.34",
        "5.15.0-35.36",
        "5.15.0-37.39",
        "5.15.0-39.42",
        "5.15.0-40.43",
        "5.15.0-41.44",
        "5.15.0-43.46",
        "5.15.0-46.49",
        "5.15.0-47.53",
        "5.15.0-48.54",
        "5.15.0-50.56",
        "5.15.0-52.58",
        "5.15.0-53.59",
        "5.15.0-56.62",
        "5.15.0-57.63",
        "5.15.0-58.64",
        "5.15.0-60.66",
        "5.15.0-67.74",
        "5.15.0-69.76",
        "5.15.0-70.77",
        "5.15.0-71.78",
        "5.15.0-72.79",
        "5.15.0-73.80",
        "5.15.0-75.82",
        "5.15.0-76.83",
        "5.15.0-78.85",
        "5.15.0-79.88",
        "5.15.0-82.91",
        "5.15.0-83.92",
        "5.15.0-84.93",
        "5.15.0-86.95",
        "5.15.0-87.96",
        "5.15.0-88.98",
        "5.15.0-89.99",
        "5.15.0-91.101",
        "5.15.0-92.102",
        "5.15.0-94.104",
        "5.15.0-97.107",
        "5.15.0-100.110",
        "5.15.0-101.111",
        "5.15.0-102.112",
        "5.15.0-105.115",
        "5.15.0-106.116",
        "5.15.0-107.117",
        "5.15.0-110.120",
        "5.15.0-113.123",
        "5.15.0-116.126",
        "5.15.0-117.127",
        "5.15.0-118.128",
        "5.15.0-119.129",
        "5.15.0-121.131",
        "5.15.0-122.132",
        "5.15.0-124.134",
        "5.15.0-125.135",
        "5.15.0-126.136"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.19.0-1030-lowlatency",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-buildinfo-5.19.0-1030-lowlatency-64k",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-cloud-tools-5.19.0-1030-lowlatency",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-headers-5.19.0-1030-lowlatency",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-headers-5.19.0-1030-lowlatency-64k",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-image-unsigned-5.19.0-1030-lowlatency",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-image-unsigned-5.19.0-1030-lowlatency-64k",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-lowlatency-hwe-5.19-cloud-tools-5.19.0-1030",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-lowlatency-hwe-5.19-cloud-tools-common",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-lowlatency-hwe-5.19-headers-5.19.0-1030",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-lowlatency-hwe-5.19-tools-5.19.0-1030",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-lowlatency-hwe-5.19-tools-common",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-lowlatency-hwe-5.19-tools-host",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-modules-5.19.0-1030-lowlatency",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-modules-5.19.0-1030-lowlatency-64k",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-modules-ipu6-5.19.0-1030-lowlatency",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-modules-ivsc-5.19.0-1030-lowlatency",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-modules-iwlwifi-5.19.0-1030-lowlatency",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-tools-5.19.0-1030-lowlatency",
            "binary_version": "5.19.0-1030.30"
          },
          {
            "binary_name": "linux-tools-5.19.0-1030-lowlatency-64k",
            "binary_version": "5.19.0-1030.30"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-lowlatency-hwe-5.19",
        "purl": "pkg:deb/ubuntu/linux-lowlatency-hwe-5.19@5.19.0-1030.30?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.19.0-1017.18~22.04.1",
        "5.19.0-1018.19~22.04.1",
        "5.19.0-1021.22~22.04.1",
        "5.19.0-1022.23~22.04.1",
        "5.19.0-1023.24~22.04.1",
        "5.19.0-1024.25~22.04.1",
        "5.19.0-1025.26~22.04.1",
        "5.19.0-1027.28~22.04.1",
        "5.19.0-1028.29~22.04.1",
        "5.19.0-1030.30"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.2.0-1018-lowlatency",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.2.0-1018-lowlatency-64k",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-6.2.0-1018-lowlatency",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.2.0-1018-lowlatency",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.2.0-1018-lowlatency-64k",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.2.0-1018-lowlatency",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.2.0-1018-lowlatency-64k",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-6.2-cloud-tools-6.2.0-1018",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-6.2-cloud-tools-common",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-6.2-headers-6.2.0-1018",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-6.2-tools-6.2.0-1018",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-6.2-tools-common",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-6.2-tools-host",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.2.0-1018-lowlatency",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.2.0-1018-lowlatency-64k",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-modules-ipu6-6.2.0-1018-lowlatency",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-modules-ivsc-6.2.0-1018-lowlatency",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.2.0-1018-lowlatency",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.2.0-1018-lowlatency",
            "binary_version": "6.2.0-1018.18~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.2.0-1018-lowlatency-64k",
            "binary_version": "6.2.0-1018.18~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-lowlatency-hwe-6.2",
        "purl": "pkg:deb/ubuntu/linux-lowlatency-hwe-6.2@6.2.0-1018.18~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.2.0-1008.8~22.04.1",
        "6.2.0-1009.9~22.04.1",
        "6.2.0-1011.11~22.04.1",
        "6.2.0-1012.12~22.04.1",
        "6.2.0-1013.13~22.04.1",
        "6.2.0-1014.14~22.04.1",
        "6.2.0-1015.15~22.04.1",
        "6.2.0-1016.16~22.04.1",
        "6.2.0-1017.17~22.04.1",
        "6.2.0-1018.18~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.5.0-45-lowlatency",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.5.0-45-lowlatency-64k",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-6.5.0-45-lowlatency",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.5.0-45-lowlatency",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.5.0-45-lowlatency-64k",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.5.0-45-lowlatency",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.5.0-45-lowlatency-64k",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-6.5-cloud-tools-6.5.0-45",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-6.5-cloud-tools-common",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-6.5-headers-6.5.0-45",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-6.5-lib-rust-6.5.0-45-lowlatency",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-6.5-tools-6.5.0-45",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-6.5-tools-common",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-6.5-tools-host",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.5.0-45-lowlatency",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.5.0-45-lowlatency-64k",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.5.0-45-lowlatency",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.5.0-45-lowlatency",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.5.0-45-lowlatency-64k",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-lowlatency-hwe-6.5",
        "purl": "pkg:deb/ubuntu/linux-lowlatency-hwe-6.5@6.5.0-45.45.1~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-14.14.1~22.04.1",
        "6.5.0-15.15.1.1~22.04.1",
        "6.5.0-17.17.1.1.1~22.04.1",
        "6.5.0-21.21.1~22.04.1",
        "6.5.0-25.25.1~22.04.1",
        "6.5.0-26.26.1~22.04.1",
        "6.5.0-27.28.1~22.04.1",
        "6.5.0-28.29.1~22.04.1",
        "6.5.0-35.35.1~22.04.1",
        "6.5.0-41.41.1~22.04.1",
        "6.5.0-42.42.1~22.04.1",
        "6.5.0-44.44.1~22.04.1",
        "6.5.0-45.45.1~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-56-lowlatency",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.8.0-56-lowlatency-64k",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-6.8.0-56-lowlatency",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-56-lowlatency",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-56-lowlatency-64k",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-56-lowlatency",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-56-lowlatency-64k",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-6.8-cloud-tools-6.8.0-56",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-6.8-headers-6.8.0-56",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-6.8-lib-rust-6.8.0-56-lowlatency",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-lowlatency-hwe-6.8-tools-6.8.0-56",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-56-lowlatency",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-56-lowlatency-64k",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.8.0-56-lowlatency",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-56-lowlatency",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-56-lowlatency-64k",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-lowlatency-hwe-6.8",
        "purl": "pkg:deb/ubuntu/linux-lowlatency-hwe-6.8@6.8.0-56.58.1~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-56.58.1~22.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-38.38.1~22.04.2",
        "6.8.0-40.40.1~22.04.1",
        "6.8.0-44.44.1~22.04.1",
        "6.8.0-45.45.1~22.04.1",
        "6.8.0-47.47.1~22.04.1",
        "6.8.0-48.48.3~22.04.1",
        "6.8.0-49.49.1~22.04.1",
        "6.8.0-50.51.1~22.04.1",
        "6.8.0-51.52.1~22.04.1",
        "6.8.0-52.53.1~22.04.1",
        "6.8.0-54.56.1~22.04.1",
        "6.8.0-55.57.1~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1068-nvidia",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-1068-nvidia-lowlatency",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-1068-nvidia",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-1068-nvidia-lowlatency",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-headers-5.15.0-1068-nvidia",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-headers-5.15.0-1068-nvidia-lowlatency",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1068-nvidia",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1068-nvidia-lowlatency",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-modules-5.15.0-1068-nvidia",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-modules-5.15.0-1068-nvidia-lowlatency",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1068-nvidia",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-modules-nvidia-fs-5.15.0-1068-nvidia",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-modules-nvidia-fs-5.15.0-1068-nvidia-lowlatency",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-nvidia-cloud-tools-5.15.0-1068",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-nvidia-cloud-tools-common",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-nvidia-headers-5.15.0-1068",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-nvidia-tools-5.15.0-1068",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-nvidia-tools-common",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-nvidia-tools-host",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-tools-5.15.0-1068-nvidia",
            "binary_version": "5.15.0-1068.69"
          },
          {
            "binary_name": "linux-tools-5.15.0-1068-nvidia-lowlatency",
            "binary_version": "5.15.0-1068.69"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-nvidia",
        "purl": "pkg:deb/ubuntu/linux-nvidia@5.15.0-1068.69?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1068.69"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1005.5",
        "5.15.0-1007.7",
        "5.15.0-1010.10",
        "5.15.0-1015.15",
        "5.15.0-1017.17",
        "5.15.0-1018.18",
        "5.15.0-1023.23",
        "5.15.0-1025.25",
        "5.15.0-1026.26",
        "5.15.0-1027.27",
        "5.15.0-1028.28",
        "5.15.0-1029.29",
        "5.15.0-1030.30",
        "5.15.0-1031.31",
        "5.15.0-1032.32",
        "5.15.0-1033.33",
        "5.15.0-1037.37",
        "5.15.0-1039.39",
        "5.15.0-1040.40",
        "5.15.0-1041.41",
        "5.15.0-1042.42",
        "5.15.0-1043.43",
        "5.15.0-1044.44",
        "5.15.0-1045.45",
        "5.15.0-1046.46",
        "5.15.0-1047.47",
        "5.15.0-1048.48",
        "5.15.0-1053.54",
        "5.15.0-1054.55",
        "5.15.0-1055.56",
        "5.15.0-1058.59",
        "5.15.0-1059.60",
        "5.15.0-1060.61",
        "5.15.0-1061.62",
        "5.15.0-1062.63",
        "5.15.0-1063.64",
        "5.15.0-1064.65",
        "5.15.0-1065.66",
        "5.15.0-1066.67",
        "5.15.0-1067.68"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.2.0-1015-nvidia",
            "binary_version": "6.2.0-1015.15"
          },
          {
            "binary_name": "linux-buildinfo-6.2.0-1015-nvidia-64k",
            "binary_version": "6.2.0-1015.15"
          },
          {
            "binary_name": "linux-headers-6.2.0-1015-nvidia",
            "binary_version": "6.2.0-1015.15"
          },
          {
            "binary_name": "linux-headers-6.2.0-1015-nvidia-64k",
            "binary_version": "6.2.0-1015.15"
          },
          {
            "binary_name": "linux-image-unsigned-6.2.0-1015-nvidia",
            "binary_version": "6.2.0-1015.15"
          },
          {
            "binary_name": "linux-image-unsigned-6.2.0-1015-nvidia-64k",
            "binary_version": "6.2.0-1015.15"
          },
          {
            "binary_name": "linux-modules-6.2.0-1015-nvidia",
            "binary_version": "6.2.0-1015.15"
          },
          {
            "binary_name": "linux-modules-6.2.0-1015-nvidia-64k",
            "binary_version": "6.2.0-1015.15"
          },
          {
            "binary_name": "linux-modules-extra-6.2.0-1015-nvidia",
            "binary_version": "6.2.0-1015.15"
          },
          {
            "binary_name": "linux-modules-nvidia-fs-6.2.0-1015-nvidia",
            "binary_version": "6.2.0-1015.15"
          },
          {
            "binary_name": "linux-modules-nvidia-fs-6.2.0-1015-nvidia-64k",
            "binary_version": "6.2.0-1015.15"
          },
          {
            "binary_name": "linux-nvidia-6.2-headers-6.2.0-1015",
            "binary_version": "6.2.0-1015.15"
          },
          {
            "binary_name": "linux-nvidia-6.2-tools-6.2.0-1015",
            "binary_version": "6.2.0-1015.15"
          },
          {
            "binary_name": "linux-nvidia-6.2-tools-host",
            "binary_version": "6.2.0-1015.15"
          },
          {
            "binary_name": "linux-tools-6.2.0-1015-nvidia",
            "binary_version": "6.2.0-1015.15"
          },
          {
            "binary_name": "linux-tools-6.2.0-1015-nvidia-64k",
            "binary_version": "6.2.0-1015.15"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-nvidia-6.2",
        "purl": "pkg:deb/ubuntu/linux-nvidia-6.2@6.2.0-1015.15?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.2.0-1003.3~22.04.1",
        "6.2.0-1009.9",
        "6.2.0-1010.10",
        "6.2.0-1011.11",
        "6.2.0-1012.12",
        "6.2.0-1013.13",
        "6.2.0-1015.15"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.5.0-1024-nvidia",
            "binary_version": "6.5.0-1024.25"
          },
          {
            "binary_name": "linux-buildinfo-6.5.0-1024-nvidia-64k",
            "binary_version": "6.5.0-1024.25"
          },
          {
            "binary_name": "linux-headers-6.5.0-1024-nvidia",
            "binary_version": "6.5.0-1024.25"
          },
          {
            "binary_name": "linux-headers-6.5.0-1024-nvidia-64k",
            "binary_version": "6.5.0-1024.25"
          },
          {
            "binary_name": "linux-image-unsigned-6.5.0-1024-nvidia",
            "binary_version": "6.5.0-1024.25"
          },
          {
            "binary_name": "linux-image-unsigned-6.5.0-1024-nvidia-64k",
            "binary_version": "6.5.0-1024.25"
          },
          {
            "binary_name": "linux-modules-6.5.0-1024-nvidia",
            "binary_version": "6.5.0-1024.25"
          },
          {
            "binary_name": "linux-modules-6.5.0-1024-nvidia-64k",
            "binary_version": "6.5.0-1024.25"
          },
          {
            "binary_name": "linux-modules-extra-6.5.0-1024-nvidia",
            "binary_version": "6.5.0-1024.25"
          },
          {
            "binary_name": "linux-modules-nvidia-fs-6.5.0-1024-nvidia",
            "binary_version": "6.5.0-1024.25"
          },
          {
            "binary_name": "linux-modules-nvidia-fs-6.5.0-1024-nvidia-64k",
            "binary_version": "6.5.0-1024.25"
          },
          {
            "binary_name": "linux-nvidia-6.5-headers-6.5.0-1024",
            "binary_version": "6.5.0-1024.25"
          },
          {
            "binary_name": "linux-nvidia-6.5-tools-6.5.0-1024",
            "binary_version": "6.5.0-1024.25"
          },
          {
            "binary_name": "linux-nvidia-6.5-tools-host",
            "binary_version": "6.5.0-1024.25"
          },
          {
            "binary_name": "linux-tools-6.5.0-1024-nvidia",
            "binary_version": "6.5.0-1024.25"
          },
          {
            "binary_name": "linux-tools-6.5.0-1024-nvidia-64k",
            "binary_version": "6.5.0-1024.25"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-nvidia-6.5",
        "purl": "pkg:deb/ubuntu/linux-nvidia-6.5@6.5.0-1024.25?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-1004.4",
        "6.5.0-1007.7",
        "6.5.0-1013.13",
        "6.5.0-1014.14",
        "6.5.0-1015.15",
        "6.5.0-1018.18",
        "6.5.0-1019.19",
        "6.5.0-1021.22",
        "6.5.0-1022.23",
        "6.5.0-1023.24",
        "6.5.0-1024.25"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-1024-nvidia",
            "binary_version": "6.8.0-1024.27~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.8.0-1024-nvidia-64k",
            "binary_version": "6.8.0-1024.27~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-1024-nvidia",
            "binary_version": "6.8.0-1024.27~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-1024-nvidia-64k",
            "binary_version": "6.8.0-1024.27~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1024-nvidia",
            "binary_version": "6.8.0-1024.27~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1024-nvidia-64k",
            "binary_version": "6.8.0-1024.27~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-1024-nvidia",
            "binary_version": "6.8.0-1024.27~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-1024-nvidia-64k",
            "binary_version": "6.8.0-1024.27~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1024-nvidia",
            "binary_version": "6.8.0-1024.27~22.04.1"
          },
          {
            "binary_name": "linux-modules-nvidia-fs-6.8.0-1024-nvidia",
            "binary_version": "6.8.0-1024.27~22.04.1"
          },
          {
            "binary_name": "linux-modules-nvidia-fs-6.8.0-1024-nvidia-64k",
            "binary_version": "6.8.0-1024.27~22.04.1"
          },
          {
            "binary_name": "linux-nvidia-6.8-headers-6.8.0-1024",
            "binary_version": "6.8.0-1024.27~22.04.1"
          },
          {
            "binary_name": "linux-nvidia-6.8-tools-6.8.0-1024",
            "binary_version": "6.8.0-1024.27~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-1024-nvidia",
            "binary_version": "6.8.0-1024.27~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-1024-nvidia-64k",
            "binary_version": "6.8.0-1024.27~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-nvidia-6.8",
        "purl": "pkg:deb/ubuntu/linux-nvidia-6.8@6.8.0-1024.27~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1024.27~22.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-1008.8~22.04.1",
        "6.8.0-1009.9~22.04.1",
        "6.8.0-1010.10~22.04.1",
        "6.8.0-1011.11~22.04.1",
        "6.8.0-1012.12~22.04.1",
        "6.8.0-1013.14~22.04.1",
        "6.8.0-1014.15~22.04.1",
        "6.8.0-1015.16~22.04.1",
        "6.8.0-1017.19~22.04.1",
        "6.8.0-1018.20~22.04.1",
        "6.8.0-1019.21~22.04.1",
        "6.8.0-1020.22~22.04.1",
        "6.8.0-1021.23~22.04.1",
        "6.8.0-1022.25~22.04.2",
        "6.8.0-1023.26~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1032-nvidia-tegra",
            "binary_version": "5.15.0-1032.32"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-1032-nvidia-tegra-rt",
            "binary_version": "5.15.0-1032.32"
          },
          {
            "binary_name": "linux-headers-5.15.0-1032-nvidia-tegra",
            "binary_version": "5.15.0-1032.32"
          },
          {
            "binary_name": "linux-headers-5.15.0-1032-nvidia-tegra-rt",
            "binary_version": "5.15.0-1032.32"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1032-nvidia-tegra",
            "binary_version": "5.15.0-1032.32"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1032-nvidia-tegra-rt",
            "binary_version": "5.15.0-1032.32"
          },
          {
            "binary_name": "linux-modules-5.15.0-1032-nvidia-tegra",
            "binary_version": "5.15.0-1032.32"
          },
          {
            "binary_name": "linux-modules-5.15.0-1032-nvidia-tegra-rt",
            "binary_version": "5.15.0-1032.32"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1032-nvidia-tegra",
            "binary_version": "5.15.0-1032.32"
          },
          {
            "binary_name": "linux-nvidia-tegra-headers-5.15.0-1032",
            "binary_version": "5.15.0-1032.32"
          },
          {
            "binary_name": "linux-nvidia-tegra-tools-5.15.0-1032",
            "binary_version": "5.15.0-1032.32"
          },
          {
            "binary_name": "linux-tools-5.15.0-1032-nvidia-tegra",
            "binary_version": "5.15.0-1032.32"
          },
          {
            "binary_name": "linux-tools-5.15.0-1032-nvidia-tegra-rt",
            "binary_version": "5.15.0-1032.32"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-nvidia-tegra",
        "purl": "pkg:deb/ubuntu/linux-nvidia-tegra@5.15.0-1032.32?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1032.32"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1009.9",
        "5.15.0-1010.10",
        "5.15.0-1012.12",
        "5.15.0-1013.13",
        "5.15.0-1014.14",
        "5.15.0-1015.15",
        "5.15.0-1016.16",
        "5.15.0-1017.17",
        "5.15.0-1018.18",
        "5.15.0-1019.19",
        "5.15.0-1020.20",
        "5.15.0-1021.21",
        "5.15.0-1022.22",
        "5.15.0-1025.25",
        "5.15.0-1026.26",
        "5.15.0-1027.27",
        "5.15.0-1028.28",
        "5.15.0-1030.30"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1020-nvidia-tegra-igx",
            "binary_version": "5.15.0-1020.20"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-1020-nvidia-tegra-igx-rt",
            "binary_version": "5.15.0-1020.20"
          },
          {
            "binary_name": "linux-headers-5.15.0-1020-nvidia-tegra-igx",
            "binary_version": "5.15.0-1020.20"
          },
          {
            "binary_name": "linux-headers-5.15.0-1020-nvidia-tegra-igx-rt",
            "binary_version": "5.15.0-1020.20"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1020-nvidia-tegra-igx",
            "binary_version": "5.15.0-1020.20"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1020-nvidia-tegra-igx-rt",
            "binary_version": "5.15.0-1020.20"
          },
          {
            "binary_name": "linux-modules-5.15.0-1020-nvidia-tegra-igx",
            "binary_version": "5.15.0-1020.20"
          },
          {
            "binary_name": "linux-modules-5.15.0-1020-nvidia-tegra-igx-rt",
            "binary_version": "5.15.0-1020.20"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1020-nvidia-tegra-igx",
            "binary_version": "5.15.0-1020.20"
          },
          {
            "binary_name": "linux-nvidia-tegra-igx-headers-5.15.0-1020",
            "binary_version": "5.15.0-1020.20"
          },
          {
            "binary_name": "linux-nvidia-tegra-igx-tools-5.15.0-1020",
            "binary_version": "5.15.0-1020.20"
          },
          {
            "binary_name": "linux-tools-5.15.0-1020-nvidia-tegra-igx",
            "binary_version": "5.15.0-1020.20"
          },
          {
            "binary_name": "linux-tools-5.15.0-1020-nvidia-tegra-igx-rt",
            "binary_version": "5.15.0-1020.20"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-nvidia-tegra-igx",
        "purl": "pkg:deb/ubuntu/linux-nvidia-tegra-igx@5.15.0-1020.20?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1020.20"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1001.1",
        "5.15.0-1002.2",
        "5.15.0-1004.4",
        "5.15.0-1005.5",
        "5.15.0-1006.6",
        "5.15.0-1007.7",
        "5.15.0-1008.8",
        "5.15.0-1009.9",
        "5.15.0-1012.12",
        "5.15.0-1013.13",
        "5.15.0-1015.15",
        "5.15.0-1016.16",
        "5.15.0-1018.18",
        "5.15.0-1019.19"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.17.0-1035-oem",
            "binary_version": "5.17.0-1035.36"
          },
          {
            "binary_name": "linux-headers-5.17.0-1035-oem",
            "binary_version": "5.17.0-1035.36"
          },
          {
            "binary_name": "linux-image-unsigned-5.17.0-1035-oem",
            "binary_version": "5.17.0-1035.36"
          },
          {
            "binary_name": "linux-modules-5.17.0-1035-oem",
            "binary_version": "5.17.0-1035.36"
          },
          {
            "binary_name": "linux-modules-ipu6-5.17.0-1035-oem",
            "binary_version": "5.17.0-1035.36"
          },
          {
            "binary_name": "linux-modules-ivsc-5.17.0-1035-oem",
            "binary_version": "5.17.0-1035.36"
          },
          {
            "binary_name": "linux-modules-iwlwifi-5.17.0-1035-oem",
            "binary_version": "5.17.0-1035.36"
          },
          {
            "binary_name": "linux-oem-5.17-headers-5.17.0-1035",
            "binary_version": "5.17.0-1035.36"
          },
          {
            "binary_name": "linux-oem-5.17-tools-5.17.0-1035",
            "binary_version": "5.17.0-1035.36"
          },
          {
            "binary_name": "linux-oem-5.17-tools-host",
            "binary_version": "5.17.0-1035.36"
          },
          {
            "binary_name": "linux-tools-5.17.0-1035-oem",
            "binary_version": "5.17.0-1035.36"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-oem-5.17",
        "purl": "pkg:deb/ubuntu/linux-oem-5.17@5.17.0-1035.36?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.17.0-1003.3",
        "5.17.0-1004.4",
        "5.17.0-1006.6",
        "5.17.0-1011.12",
        "5.17.0-1012.13",
        "5.17.0-1013.14",
        "5.17.0-1014.15",
        "5.17.0-1015.16",
        "5.17.0-1016.17",
        "5.17.0-1017.18",
        "5.17.0-1018.19",
        "5.17.0-1019.20",
        "5.17.0-1020.21",
        "5.17.0-1021.22",
        "5.17.0-1024.25",
        "5.17.0-1025.26",
        "5.17.0-1026.27",
        "5.17.0-1027.28",
        "5.17.0-1028.29",
        "5.17.0-1029.30",
        "5.17.0-1030.31",
        "5.17.0-1031.32",
        "5.17.0-1032.33",
        "5.17.0-1033.34",
        "5.17.0-1034.35",
        "5.17.0-1035.36"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.0.0-1021-oem",
            "binary_version": "6.0.0-1021.21"
          },
          {
            "binary_name": "linux-headers-6.0.0-1021-oem",
            "binary_version": "6.0.0-1021.21"
          },
          {
            "binary_name": "linux-image-unsigned-6.0.0-1021-oem",
            "binary_version": "6.0.0-1021.21"
          },
          {
            "binary_name": "linux-modules-6.0.0-1021-oem",
            "binary_version": "6.0.0-1021.21"
          },
          {
            "binary_name": "linux-modules-ipu6-6.0.0-1021-oem",
            "binary_version": "6.0.0-1021.21"
          },
          {
            "binary_name": "linux-modules-ivsc-6.0.0-1021-oem",
            "binary_version": "6.0.0-1021.21"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.0.0-1021-oem",
            "binary_version": "6.0.0-1021.21"
          },
          {
            "binary_name": "linux-oem-6.0-headers-6.0.0-1021",
            "binary_version": "6.0.0-1021.21"
          },
          {
            "binary_name": "linux-oem-6.0-tools-6.0.0-1021",
            "binary_version": "6.0.0-1021.21"
          },
          {
            "binary_name": "linux-oem-6.0-tools-host",
            "binary_version": "6.0.0-1021.21"
          },
          {
            "binary_name": "linux-tools-6.0.0-1021-oem",
            "binary_version": "6.0.0-1021.21"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-oem-6.0",
        "purl": "pkg:deb/ubuntu/linux-oem-6.0@6.0.0-1021.21?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.0.0-1006.6",
        "6.0.0-1007.7",
        "6.0.0-1008.8",
        "6.0.0-1009.9",
        "6.0.0-1010.10",
        "6.0.0-1011.11",
        "6.0.0-1012.12",
        "6.0.0-1013.13",
        "6.0.0-1014.14",
        "6.0.0-1015.15",
        "6.0.0-1016.16",
        "6.0.0-1017.17",
        "6.0.0-1018.18",
        "6.0.0-1019.19",
        "6.0.0-1020.20",
        "6.0.0-1021.21"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.1.0-1036-oem",
            "binary_version": "6.1.0-1036.36"
          },
          {
            "binary_name": "linux-headers-6.1.0-1036-oem",
            "binary_version": "6.1.0-1036.36"
          },
          {
            "binary_name": "linux-image-unsigned-6.1.0-1036-oem",
            "binary_version": "6.1.0-1036.36"
          },
          {
            "binary_name": "linux-modules-6.1.0-1036-oem",
            "binary_version": "6.1.0-1036.36"
          },
          {
            "binary_name": "linux-modules-ipu6-6.1.0-1036-oem",
            "binary_version": "6.1.0-1036.36"
          },
          {
            "binary_name": "linux-modules-ivsc-6.1.0-1036-oem",
            "binary_version": "6.1.0-1036.36"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.1.0-1036-oem",
            "binary_version": "6.1.0-1036.36"
          },
          {
            "binary_name": "linux-oem-6.1-headers-6.1.0-1036",
            "binary_version": "6.1.0-1036.36"
          },
          {
            "binary_name": "linux-oem-6.1-tools-6.1.0-1036",
            "binary_version": "6.1.0-1036.36"
          },
          {
            "binary_name": "linux-oem-6.1-tools-host",
            "binary_version": "6.1.0-1036.36"
          },
          {
            "binary_name": "linux-tools-6.1.0-1036-oem",
            "binary_version": "6.1.0-1036.36"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-oem-6.1",
        "purl": "pkg:deb/ubuntu/linux-oem-6.1@6.1.0-1036.36?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.1.0-1004.4",
        "6.1.0-1006.6",
        "6.1.0-1007.7",
        "6.1.0-1008.8",
        "6.1.0-1009.9",
        "6.1.0-1010.10",
        "6.1.0-1012.12",
        "6.1.0-1013.13",
        "6.1.0-1014.14",
        "6.1.0-1015.15",
        "6.1.0-1016.16",
        "6.1.0-1017.17",
        "6.1.0-1019.19",
        "6.1.0-1020.20",
        "6.1.0-1021.21",
        "6.1.0-1022.22",
        "6.1.0-1023.23",
        "6.1.0-1024.24",
        "6.1.0-1025.25",
        "6.1.0-1026.26",
        "6.1.0-1027.27",
        "6.1.0-1028.28",
        "6.1.0-1029.29",
        "6.1.0-1033.33",
        "6.1.0-1034.34",
        "6.1.0-1035.35",
        "6.1.0-1036.36"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.5.0-1027-oem",
            "binary_version": "6.5.0-1027.28"
          },
          {
            "binary_name": "linux-headers-6.5.0-1027-oem",
            "binary_version": "6.5.0-1027.28"
          },
          {
            "binary_name": "linux-image-unsigned-6.5.0-1027-oem",
            "binary_version": "6.5.0-1027.28"
          },
          {
            "binary_name": "linux-modules-6.5.0-1027-oem",
            "binary_version": "6.5.0-1027.28"
          },
          {
            "binary_name": "linux-modules-ipu6-6.5.0-1027-oem",
            "binary_version": "6.5.0-1027.28"
          },
          {
            "binary_name": "linux-modules-ivsc-6.5.0-1027-oem",
            "binary_version": "6.5.0-1027.28"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.5.0-1027-oem",
            "binary_version": "6.5.0-1027.28"
          },
          {
            "binary_name": "linux-modules-usbio-6.5.0-1027-oem",
            "binary_version": "6.5.0-1027.28"
          },
          {
            "binary_name": "linux-oem-6.5-headers-6.5.0-1027",
            "binary_version": "6.5.0-1027.28"
          },
          {
            "binary_name": "linux-oem-6.5-lib-rust-6.5.0-1027-oem",
            "binary_version": "6.5.0-1027.28"
          },
          {
            "binary_name": "linux-oem-6.5-tools-6.5.0-1027",
            "binary_version": "6.5.0-1027.28"
          },
          {
            "binary_name": "linux-oem-6.5-tools-host",
            "binary_version": "6.5.0-1027.28"
          },
          {
            "binary_name": "linux-tools-6.5.0-1027-oem",
            "binary_version": "6.5.0-1027.28"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-oem-6.5",
        "purl": "pkg:deb/ubuntu/linux-oem-6.5@6.5.0-1027.28?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-1003.3",
        "6.5.0-1004.4",
        "6.5.0-1006.6",
        "6.5.0-1007.7",
        "6.5.0-1008.8",
        "6.5.0-1009.10",
        "6.5.0-1011.12",
        "6.5.0-1013.14",
        "6.5.0-1014.15",
        "6.5.0-1015.16",
        "6.5.0-1016.17",
        "6.5.0-1018.19",
        "6.5.0-1019.20",
        "6.5.0-1020.21",
        "6.5.0-1022.23",
        "6.5.0-1023.24",
        "6.5.0-1024.25",
        "6.5.0-1025.26",
        "6.5.0-1027.28"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1071-oracle",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-headers-5.15.0-1071-oracle",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1071-oracle",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-modules-5.15.0-1071-oracle",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1071-oracle",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-oracle-headers-5.15.0-1071",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-oracle-tools-5.15.0-1071",
            "binary_version": "5.15.0-1071.77"
          },
          {
            "binary_name": "linux-tools-5.15.0-1071-oracle",
            "binary_version": "5.15.0-1071.77"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-oracle",
        "purl": "pkg:deb/ubuntu/linux-oracle@5.15.0-1071.77?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1071.77"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.13.0-1008.10",
        "5.15.0-1001.3",
        "5.15.0-1002.4",
        "5.15.0-1003.5",
        "5.15.0-1006.8",
        "5.15.0-1007.9",
        "5.15.0-1009.12",
        "5.15.0-1011.15",
        "5.15.0-1013.17",
        "5.15.0-1016.20",
        "5.15.0-1017.22",
        "5.15.0-1018.23",
        "5.15.0-1019.24",
        "5.15.0-1021.27",
        "5.15.0-1022.28",
        "5.15.0-1025.31",
        "5.15.0-1026.32",
        "5.15.0-1027.33",
        "5.15.0-1029.35",
        "5.15.0-1030.36",
        "5.15.0-1032.38",
        "5.15.0-1033.39",
        "5.15.0-1034.40",
        "5.15.0-1035.41",
        "5.15.0-1036.42",
        "5.15.0-1037.43",
        "5.15.0-1038.44",
        "5.15.0-1039.45",
        "5.15.0-1040.46",
        "5.15.0-1041.47",
        "5.15.0-1042.48",
        "5.15.0-1044.50",
        "5.15.0-1045.51",
        "5.15.0-1046.52",
        "5.15.0-1047.53",
        "5.15.0-1048.54",
        "5.15.0-1049.55",
        "5.15.0-1050.56",
        "5.15.0-1051.57",
        "5.15.0-1052.58",
        "5.15.0-1053.59",
        "5.15.0-1054.60",
        "5.15.0-1055.61",
        "5.15.0-1058.64",
        "5.15.0-1059.65",
        "5.15.0-1060.66",
        "5.15.0-1061.67",
        "5.15.0-1062.68",
        "5.15.0-1063.69",
        "5.15.0-1064.70",
        "5.15.0-1065.71",
        "5.15.0-1066.72",
        "5.15.0-1067.73",
        "5.15.0-1068.74",
        "5.15.0-1069.75",
        "5.15.0-1070.76"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.5.0-1027-oracle",
            "binary_version": "6.5.0-1027.27~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.5.0-1027-oracle-64k",
            "binary_version": "6.5.0-1027.27~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.5.0-1027-oracle",
            "binary_version": "6.5.0-1027.27~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.5.0-1027-oracle-64k",
            "binary_version": "6.5.0-1027.27~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.5.0-1027-oracle",
            "binary_version": "6.5.0-1027.27~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.5.0-1027-oracle-64k",
            "binary_version": "6.5.0-1027.27~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.5.0-1027-oracle",
            "binary_version": "6.5.0-1027.27~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.5.0-1027-oracle-64k",
            "binary_version": "6.5.0-1027.27~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.5.0-1027-oracle",
            "binary_version": "6.5.0-1027.27~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.5.0-1027-oracle-64k",
            "binary_version": "6.5.0-1027.27~22.04.1"
          },
          {
            "binary_name": "linux-oracle-6.5-headers-6.5.0-1027",
            "binary_version": "6.5.0-1027.27~22.04.1"
          },
          {
            "binary_name": "linux-oracle-6.5-tools-6.5.0-1027",
            "binary_version": "6.5.0-1027.27~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.5.0-1027-oracle",
            "binary_version": "6.5.0-1027.27~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.5.0-1027-oracle-64k",
            "binary_version": "6.5.0-1027.27~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-oracle-6.5",
        "purl": "pkg:deb/ubuntu/linux-oracle-6.5@6.5.0-1027.27~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-1013.13~22.04.4",
        "6.5.0-1014.14~22.04.1",
        "6.5.0-1015.15~22.04.1",
        "6.5.0-1016.16~22.04.1",
        "6.5.0-1018.18~22.04.1",
        "6.5.0-1019.19~22.04.1",
        "6.5.0-1020.20~22.04.1",
        "6.5.0-1021.21~22.04.1",
        "6.5.0-1023.23~22.04.1",
        "6.5.0-1024.24~22.04.1",
        "6.5.0-1025.25~22.04.1",
        "6.5.0-1026.26~22.04.1",
        "6.5.0-1027.27~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-1022-oracle",
            "binary_version": "6.8.0-1022.23~22.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.8.0-1022-oracle-64k",
            "binary_version": "6.8.0-1022.23~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-1022-oracle",
            "binary_version": "6.8.0-1022.23~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-1022-oracle-64k",
            "binary_version": "6.8.0-1022.23~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1022-oracle",
            "binary_version": "6.8.0-1022.23~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1022-oracle-64k",
            "binary_version": "6.8.0-1022.23~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-1022-oracle",
            "binary_version": "6.8.0-1022.23~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-1022-oracle-64k",
            "binary_version": "6.8.0-1022.23~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1022-oracle",
            "binary_version": "6.8.0-1022.23~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1022-oracle-64k",
            "binary_version": "6.8.0-1022.23~22.04.1"
          },
          {
            "binary_name": "linux-oracle-6.8-headers-6.8.0-1022",
            "binary_version": "6.8.0-1022.23~22.04.1"
          },
          {
            "binary_name": "linux-oracle-6.8-tools-6.8.0-1022",
            "binary_version": "6.8.0-1022.23~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-1022-oracle",
            "binary_version": "6.8.0-1022.23~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-1022-oracle-64k",
            "binary_version": "6.8.0-1022.23~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-oracle-6.8",
        "purl": "pkg:deb/ubuntu/linux-oracle-6.8@6.8.0-1022.23~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1022.23~22.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-1006.6~22.04.3",
        "6.8.0-1008.8~22.04.1",
        "6.8.0-1010.10~22.04.1",
        "6.8.0-1011.11~22.04.1",
        "6.8.0-1012.12~22.04.1",
        "6.8.0-1013.13~22.04.1",
        "6.8.0-1014.14~22.04.1",
        "6.8.0-1015.15~22.04.1",
        "6.8.0-1016.17~22.04.1",
        "6.8.0-1017.18~22.04.1",
        "6.8.0-1018.19~22.04.1",
        "6.8.0-1019.20~22.04.1",
        "6.8.0-1020.21~22.04.1",
        "6.8.0-1021.22~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1066-raspi",
            "binary_version": "5.15.0-1066.69"
          },
          {
            "binary_name": "linux-headers-5.15.0-1066-raspi",
            "binary_version": "5.15.0-1066.69"
          },
          {
            "binary_name": "linux-image-5.15.0-1066-raspi",
            "binary_version": "5.15.0-1066.69"
          },
          {
            "binary_name": "linux-modules-5.15.0-1066-raspi",
            "binary_version": "5.15.0-1066.69"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1066-raspi",
            "binary_version": "5.15.0-1066.69"
          },
          {
            "binary_name": "linux-raspi-headers-5.15.0-1066",
            "binary_version": "5.15.0-1066.69"
          },
          {
            "binary_name": "linux-raspi-tools-5.15.0-1066",
            "binary_version": "5.15.0-1066.69"
          },
          {
            "binary_name": "linux-tools-5.15.0-1066-raspi",
            "binary_version": "5.15.0-1066.69"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-raspi",
        "purl": "pkg:deb/ubuntu/linux-raspi@5.15.0-1066.69?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1066.69"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.13.0-1008.9",
        "5.15.0-1002.2",
        "5.15.0-1003.3",
        "5.15.0-1004.4",
        "5.15.0-1005.5",
        "5.15.0-1006.6",
        "5.15.0-1008.8",
        "5.15.0-1011.13",
        "5.15.0-1012.14",
        "5.15.0-1013.15",
        "5.15.0-1014.16",
        "5.15.0-1015.17",
        "5.15.0-1016.18",
        "5.15.0-1017.19",
        "5.15.0-1018.20",
        "5.15.0-1021.23",
        "5.15.0-1022.24",
        "5.15.0-1023.25",
        "5.15.0-1024.26",
        "5.15.0-1025.27",
        "5.15.0-1026.28",
        "5.15.0-1027.29",
        "5.15.0-1028.30",
        "5.15.0-1029.31",
        "5.15.0-1030.32",
        "5.15.0-1032.35",
        "5.15.0-1033.36",
        "5.15.0-1034.37",
        "5.15.0-1035.38",
        "5.15.0-1036.39",
        "5.15.0-1037.40",
        "5.15.0-1038.41",
        "5.15.0-1040.43",
        "5.15.0-1041.44",
        "5.15.0-1042.45",
        "5.15.0-1043.46",
        "5.15.0-1044.47",
        "5.15.0-1045.48",
        "5.15.0-1046.49",
        "5.15.0-1047.50",
        "5.15.0-1048.51",
        "5.15.0-1049.52",
        "5.15.0-1050.53",
        "5.15.0-1053.56",
        "5.15.0-1054.57",
        "5.15.0-1055.58",
        "5.15.0-1058.61",
        "5.15.0-1059.62",
        "5.15.0-1060.63",
        "5.15.0-1061.64",
        "5.15.0-1062.65",
        "5.15.0-1063.66",
        "5.15.0-1064.67",
        "5.15.0-1065.68"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1032-realtime",
            "binary_version": "5.15.0-1032.35"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-1032-realtime",
            "binary_version": "5.15.0-1032.35"
          },
          {
            "binary_name": "linux-headers-5.15.0-1032-realtime",
            "binary_version": "5.15.0-1032.35"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1032-realtime",
            "binary_version": "5.15.0-1032.35"
          },
          {
            "binary_name": "linux-modules-5.15.0-1032-realtime",
            "binary_version": "5.15.0-1032.35"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1032-realtime",
            "binary_version": "5.15.0-1032.35"
          },
          {
            "binary_name": "linux-realtime-cloud-tools-5.15.0-1032",
            "binary_version": "5.15.0-1032.35"
          },
          {
            "binary_name": "linux-realtime-cloud-tools-common",
            "binary_version": "5.15.0-1032.35"
          },
          {
            "binary_name": "linux-realtime-headers-5.15.0-1032",
            "binary_version": "5.15.0-1032.35"
          },
          {
            "binary_name": "linux-realtime-tools-5.15.0-1032",
            "binary_version": "5.15.0-1032.35"
          },
          {
            "binary_name": "linux-realtime-tools-common",
            "binary_version": "5.15.0-1032.35"
          },
          {
            "binary_name": "linux-realtime-tools-host",
            "binary_version": "5.15.0-1032.35"
          },
          {
            "binary_name": "linux-tools-5.15.0-1032-realtime",
            "binary_version": "5.15.0-1032.35"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-realtime",
        "purl": "pkg:deb/ubuntu/linux-realtime@5.15.0-1032.35?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1032.35"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1028-generic",
            "binary_version": "5.15.0-1028.32"
          },
          {
            "binary_name": "linux-headers-5.15.0-1028-generic",
            "binary_version": "5.15.0-1028.32"
          },
          {
            "binary_name": "linux-image-5.15.0-1028-generic",
            "binary_version": "5.15.0-1028.32"
          },
          {
            "binary_name": "linux-modules-5.15.0-1028-generic",
            "binary_version": "5.15.0-1028.32"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1028-generic",
            "binary_version": "5.15.0-1028.32"
          },
          {
            "binary_name": "linux-riscv-headers-5.15.0-1028",
            "binary_version": "5.15.0-1028.32"
          },
          {
            "binary_name": "linux-riscv-tools-5.15.0-1028",
            "binary_version": "5.15.0-1028.32"
          },
          {
            "binary_name": "linux-tools-5.15.0-1028-generic",
            "binary_version": "5.15.0-1028.32"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-riscv",
        "purl": "pkg:deb/ubuntu/linux-riscv@5.15.0-1028.32?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.13.0-1004.4",
        "5.13.0-1006.6+22.04.1",
        "5.13.0-1007.7+22.04.1",
        "5.13.0-1010.11+22.04.1",
        "5.15.0-1004.4",
        "5.15.0-1005.5",
        "5.15.0-1006.6",
        "5.15.0-1007.7",
        "5.15.0-1008.8",
        "5.15.0-1011.12",
        "5.15.0-1012.13",
        "5.15.0-1014.16",
        "5.15.0-1015.17",
        "5.15.0-1016.18",
        "5.15.0-1017.19",
        "5.15.0-1018.21",
        "5.15.0-1019.22",
        "5.15.0-1020.23",
        "5.15.0-1022.26",
        "5.15.0-1023.27",
        "5.15.0-1026.30",
        "5.15.0-1027.31",
        "5.15.0-1028.32"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.19.0-1021-generic",
            "binary_version": "5.19.0-1021.23~22.04.1"
          },
          {
            "binary_name": "linux-headers-5.19.0-1021-generic",
            "binary_version": "5.19.0-1021.23~22.04.1"
          },
          {
            "binary_name": "linux-image-5.19.0-1021-generic",
            "binary_version": "5.19.0-1021.23~22.04.1"
          },
          {
            "binary_name": "linux-modules-5.19.0-1021-generic",
            "binary_version": "5.19.0-1021.23~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.19.0-1021-generic",
            "binary_version": "5.19.0-1021.23~22.04.1"
          },
          {
            "binary_name": "linux-riscv-5.19-headers-5.19.0-1021",
            "binary_version": "5.19.0-1021.23~22.04.1"
          },
          {
            "binary_name": "linux-riscv-5.19-tools-5.19.0-1021",
            "binary_version": "5.19.0-1021.23~22.04.1"
          },
          {
            "binary_name": "linux-tools-5.19.0-1021-generic",
            "binary_version": "5.19.0-1021.23~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-riscv-5.19",
        "purl": "pkg:deb/ubuntu/linux-riscv-5.19@5.19.0-1021.23~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.19.0-1012.13~22.04.1",
        "5.19.0-1015.16~22.04.1",
        "5.19.0-1016.17~22.04.1",
        "5.19.0-1017.18~22.04.1",
        "5.19.0-1018.19~22.04.1",
        "5.19.0-1019.21~22.04.1",
        "5.19.0-1020.22~22.04.1",
        "5.19.0-1021.23~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.5.0-45-generic",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.5.0-45-generic",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-image-6.5.0-45-generic",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.5.0-45-generic",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.5.0-45-generic",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-riscv-6.5-headers-6.5.0-45",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-riscv-6.5-tools-6.5.0-45",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.5.0-45-generic",
            "binary_version": "6.5.0-45.45.1~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-riscv-6.5",
        "purl": "pkg:deb/ubuntu/linux-riscv-6.5@6.5.0-45.45.1~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-17.17.1.1~22.04.1",
        "6.5.0-21.21.1~22.04.1",
        "6.5.0-25.25.1~22.04.1",
        "6.5.0-26.26.1~22.04.1",
        "6.5.0-27.28.1~22.04.1",
        "6.5.0-28.29.1~22.04.1",
        "6.5.0-35.35.1~22.04.1",
        "6.5.0-40.40.1~22.04.1",
        "6.5.0-42.42.1~22.04.1",
        "6.5.0-45.45.1~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-image-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-riscv-6.8-headers-6.8.0-56",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-riscv-6.8-tools-6.8.0-56",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58.1~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-riscv-6.8",
        "purl": "pkg:deb/ubuntu/linux-riscv-6.8@6.8.0-56.58.1~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-56.58.1~22.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-38.38.1~22.04.1",
        "6.8.0-39.39.1~22.04.1",
        "6.8.0-40.40.1~22.04.1",
        "6.8.0-41.41.1~22.04.1",
        "6.8.0-44.44.1~22.04.1",
        "6.8.0-47.47.1~22.04.1",
        "6.8.0-48.48.1~22.04.2",
        "6.8.0-49.49.1~22.04.1",
        "6.8.0-50.51.1~22.04.1",
        "6.8.0-51.52.1~22.04.1",
        "6.8.0-52.53.1~22.04.1",
        "6.8.0-53.55.1~22.04.1",
        "6.8.0-55.57.1~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.19.0-1020-starfive",
            "binary_version": "5.19.0-1020.22~22.04.1"
          },
          {
            "binary_name": "linux-headers-5.19.0-1020-starfive",
            "binary_version": "5.19.0-1020.22~22.04.1"
          },
          {
            "binary_name": "linux-image-5.19.0-1020-starfive",
            "binary_version": "5.19.0-1020.22~22.04.1"
          },
          {
            "binary_name": "linux-modules-5.19.0-1020-starfive",
            "binary_version": "5.19.0-1020.22~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-5.19.0-1020-starfive",
            "binary_version": "5.19.0-1020.22~22.04.1"
          },
          {
            "binary_name": "linux-starfive-5.19-headers-5.19.0-1020",
            "binary_version": "5.19.0-1020.22~22.04.1"
          },
          {
            "binary_name": "linux-starfive-5.19-tools-5.19.0-1020",
            "binary_version": "5.19.0-1020.22~22.04.1"
          },
          {
            "binary_name": "linux-tools-5.19.0-1020-starfive",
            "binary_version": "5.19.0-1020.22~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-starfive-5.19",
        "purl": "pkg:deb/ubuntu/linux-starfive-5.19@5.19.0-1020.22~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.19.0-1014.16~22.04.1",
        "5.19.0-1015.17~22.04.1",
        "5.19.0-1016.18~22.04.1",
        "5.19.0-1017.19~22.04.1",
        "5.19.0-1018.20~22.04.1",
        "5.19.0-1019.21~22.04.1",
        "5.19.0-1020.22~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.2.0-1009-starfive",
            "binary_version": "6.2.0-1009.10~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.2.0-1009-starfive",
            "binary_version": "6.2.0-1009.10~22.04.1"
          },
          {
            "binary_name": "linux-image-6.2.0-1009-starfive",
            "binary_version": "6.2.0-1009.10~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.2.0-1009-starfive",
            "binary_version": "6.2.0-1009.10~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.2.0-1009-starfive",
            "binary_version": "6.2.0-1009.10~22.04.1"
          },
          {
            "binary_name": "linux-starfive-6.2-headers-6.2.0-1009",
            "binary_version": "6.2.0-1009.10~22.04.1"
          },
          {
            "binary_name": "linux-starfive-6.2-tools-6.2.0-1009",
            "binary_version": "6.2.0-1009.10~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.2.0-1009-starfive",
            "binary_version": "6.2.0-1009.10~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-starfive-6.2",
        "purl": "pkg:deb/ubuntu/linux-starfive-6.2@6.2.0-1009.10~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.2.0-1006.7~22.04.1",
        "6.2.0-1007.8~22.04.1",
        "6.2.0-1009.10~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.5.0-1018-starfive",
            "binary_version": "6.5.0-1018.19~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.5.0-1018-starfive",
            "binary_version": "6.5.0-1018.19~22.04.1"
          },
          {
            "binary_name": "linux-image-6.5.0-1018-starfive",
            "binary_version": "6.5.0-1018.19~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.5.0-1018-starfive",
            "binary_version": "6.5.0-1018.19~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.5.0-1018-starfive",
            "binary_version": "6.5.0-1018.19~22.04.1"
          },
          {
            "binary_name": "linux-starfive-6.5-headers-6.5.0-1018",
            "binary_version": "6.5.0-1018.19~22.04.1"
          },
          {
            "binary_name": "linux-starfive-6.5-tools-6.5.0-1018",
            "binary_version": "6.5.0-1018.19~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.5.0-1018-starfive",
            "binary_version": "6.5.0-1018.19~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-starfive-6.5",
        "purl": "pkg:deb/ubuntu/linux-starfive-6.5@6.5.0-1018.19~22.04.1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-1007.8~22.04.1",
        "6.5.0-1008.9~22.04.1",
        "6.5.0-1009.10~22.04.1",
        "6.5.0-1010.11~22.04.1",
        "6.5.0-1011.12~22.04.1",
        "6.5.0-1012.13~22.04.1",
        "6.5.0-1014.15~22.04.1",
        "6.5.0-1015.16~22.04.1",
        "6.5.0-1016.17~22.04.1",
        "6.5.0-1017.18~22.04.1",
        "6.5.0-1018.19~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1039-xilinx-zynqmp",
            "binary_version": "5.15.0-1039.43"
          },
          {
            "binary_name": "linux-headers-5.15.0-1039-xilinx-zynqmp",
            "binary_version": "5.15.0-1039.43"
          },
          {
            "binary_name": "linux-image-5.15.0-1039-xilinx-zynqmp",
            "binary_version": "5.15.0-1039.43"
          },
          {
            "binary_name": "linux-modules-5.15.0-1039-xilinx-zynqmp",
            "binary_version": "5.15.0-1039.43"
          },
          {
            "binary_name": "linux-tools-5.15.0-1039-xilinx-zynqmp",
            "binary_version": "5.15.0-1039.43"
          },
          {
            "binary_name": "linux-xilinx-zynqmp-headers-5.15.0-1039",
            "binary_version": "5.15.0-1039.43"
          },
          {
            "binary_name": "linux-xilinx-zynqmp-tools-5.15.0-1039",
            "binary_version": "5.15.0-1039.43"
          },
          {
            "binary_name": "linux-xilinx-zynqmp-tools-common",
            "binary_version": "5.15.0-1039.43"
          },
          {
            "binary_name": "linux-xilinx-zynqmp-tools-host",
            "binary_version": "5.15.0-1039.43"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "linux-xilinx-zynqmp",
        "purl": "pkg:deb/ubuntu/linux-xilinx-zynqmp@5.15.0-1039.43?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1039.43"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1022.26",
        "5.15.0-1023.27",
        "5.15.0-1025.29",
        "5.15.0-1027.31",
        "5.15.0-1030.34",
        "5.15.0-1031.35",
        "5.15.0-1035.39",
        "5.15.0-1036.40",
        "5.15.0-1037.41",
        "5.15.0-1038.42"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "Available for NVIDIA BlueField platforms",
        "binaries": [
          {
            "binary_name": "linux-bluefield-cloud-tools-common",
            "binary_version": "5.15.0-1057.59"
          },
          {
            "binary_name": "linux-bluefield-headers-5.15.0-1057",
            "binary_version": "5.15.0-1057.59"
          },
          {
            "binary_name": "linux-bluefield-tools-5.15.0-1057",
            "binary_version": "5.15.0-1057.59"
          },
          {
            "binary_name": "linux-bluefield-tools-host",
            "binary_version": "5.15.0-1057.59"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-1057-bluefield",
            "binary_version": "5.15.0-1057.59"
          },
          {
            "binary_name": "linux-headers-5.15.0-1057-bluefield",
            "binary_version": "5.15.0-1057.59"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1057-bluefield",
            "binary_version": "5.15.0-1057.59"
          },
          {
            "binary_name": "linux-modules-5.15.0-1057-bluefield",
            "binary_version": "5.15.0-1057.59"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1057-bluefield",
            "binary_version": "5.15.0-1057.59"
          },
          {
            "binary_name": "linux-tools-5.15.0-1057-bluefield",
            "binary_version": "5.15.0-1057.59"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Nvidia-BlueField:22.04:LTS",
        "name": "linux-bluefield",
        "purl": "pkg:deb/ubuntu/linux-bluefield@5.15.0-1057.59?arch=source\u0026distro=bluefield/jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1057.59"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1011.13",
        "5.15.0-1014.16",
        "5.15.0-1015.17",
        "5.15.0-1017.19",
        "5.15.0-1019.21",
        "5.15.0-1021.23",
        "5.15.0-1022.24",
        "5.15.0-1023.25",
        "5.15.0-1024.26",
        "5.15.0-1027.29",
        "5.15.0-1028.30",
        "5.15.0-1031.33",
        "5.15.0-1032.34",
        "5.15.0-1033.35",
        "5.15.0-1035.37",
        "5.15.0-1036.38",
        "5.15.0-1037.39",
        "5.15.0-1038.40",
        "5.15.0-1040.42",
        "5.15.0-1042.44",
        "5.15.0-1043.45",
        "5.15.0-1044.46",
        "5.15.0-1045.47",
        "5.15.0-1047.49",
        "5.15.0-1048.50",
        "5.15.0-1050.52",
        "5.15.0-1051.53",
        "5.15.0-1052.54",
        "5.15.0-1053.55",
        "5.15.0-1054.56",
        "5.15.0-1056.58"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-aws-fips-cloud-tools-5.15.0-1051",
            "binary_version": "5.15.0-1051.56+fips1"
          },
          {
            "binary_name": "linux-aws-fips-headers-5.15.0-1051",
            "binary_version": "5.15.0-1051.56+fips1"
          },
          {
            "binary_name": "linux-aws-fips-tools-5.15.0-1051",
            "binary_version": "5.15.0-1051.56+fips1"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-1051-aws-fips",
            "binary_version": "5.15.0-1051.56+fips1"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-1051-aws-fips",
            "binary_version": "5.15.0-1051.56+fips1"
          },
          {
            "binary_name": "linux-headers-5.15.0-1051-aws-fips",
            "binary_version": "5.15.0-1051.56+fips1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1051-aws-fips",
            "binary_version": "5.15.0-1051.56+fips1"
          },
          {
            "binary_name": "linux-image-unsigned-hmac-5.15.0-1051-aws-fips",
            "binary_version": "5.15.0-1051.56+fips1"
          },
          {
            "binary_name": "linux-modules-5.15.0-1051-aws-fips",
            "binary_version": "5.15.0-1051.56+fips1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1051-aws-fips",
            "binary_version": "5.15.0-1051.56+fips1"
          },
          {
            "binary_name": "linux-tools-5.15.0-1051-aws-fips",
            "binary_version": "5.15.0-1051.56+fips1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:FIPS-preview:22.04:LTS",
        "name": "linux-aws-fips",
        "purl": "pkg:deb/ubuntu/linux-aws-fips@5.15.0-1051.56+fips1?arch=source\u0026distro=fips-preview/jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1042.47+fips1",
        "5.15.0-1051.56+fips1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-azure-fips-cloud-tools-5.15.0-1053",
            "binary_version": "5.15.0-1053.61+fips1"
          },
          {
            "binary_name": "linux-azure-fips-headers-5.15.0-1053",
            "binary_version": "5.15.0-1053.61+fips1"
          },
          {
            "binary_name": "linux-azure-fips-tools-5.15.0-1053",
            "binary_version": "5.15.0-1053.61+fips1"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-1053-azure-fips",
            "binary_version": "5.15.0-1053.61+fips1"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-1053-azure-fips",
            "binary_version": "5.15.0-1053.61+fips1"
          },
          {
            "binary_name": "linux-headers-5.15.0-1053-azure-fips",
            "binary_version": "5.15.0-1053.61+fips1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1053-azure-fips",
            "binary_version": "5.15.0-1053.61+fips1"
          },
          {
            "binary_name": "linux-image-unsigned-hmac-5.15.0-1053-azure-fips",
            "binary_version": "5.15.0-1053.61+fips1"
          },
          {
            "binary_name": "linux-modules-5.15.0-1053-azure-fips",
            "binary_version": "5.15.0-1053.61+fips1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1053-azure-fips",
            "binary_version": "5.15.0-1053.61+fips1"
          },
          {
            "binary_name": "linux-tools-5.15.0-1053-azure-fips",
            "binary_version": "5.15.0-1053.61+fips1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:FIPS-preview:22.04:LTS",
        "name": "linux-azure-fips",
        "purl": "pkg:deb/ubuntu/linux-azure-fips@5.15.0-1053.61+fips1?arch=source\u0026distro=fips-preview/jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1053.61+fips1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-73-fips",
            "binary_version": "5.15.0-73.80+fips1"
          },
          {
            "binary_name": "linux-fips-headers-5.15.0-73",
            "binary_version": "5.15.0-73.80+fips1"
          },
          {
            "binary_name": "linux-fips-tools-5.15.0-73",
            "binary_version": "5.15.0-73.80+fips1"
          },
          {
            "binary_name": "linux-fips-tools-host",
            "binary_version": "5.15.0-73.80+fips1"
          },
          {
            "binary_name": "linux-headers-5.15.0-73-fips",
            "binary_version": "5.15.0-73.80+fips1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-73-fips",
            "binary_version": "5.15.0-73.80+fips1"
          },
          {
            "binary_name": "linux-image-unsigned-hmac-5.15.0-73-fips",
            "binary_version": "5.15.0-73.80+fips1"
          },
          {
            "binary_name": "linux-modules-5.15.0-73-fips",
            "binary_version": "5.15.0-73.80+fips1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-73-fips",
            "binary_version": "5.15.0-73.80+fips1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-5.15.0-73-fips",
            "binary_version": "5.15.0-73.80+fips1"
          },
          {
            "binary_name": "linux-tools-5.15.0-73-fips",
            "binary_version": "5.15.0-73.80+fips1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:FIPS-preview:22.04:LTS",
        "name": "linux-fips",
        "purl": "pkg:deb/ubuntu/linux-fips@5.15.0-73.80+fips1?arch=source\u0026distro=fips-preview/jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-73.80+fips1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1048-gcp-fips",
            "binary_version": "5.15.0-1048.56+fips1"
          },
          {
            "binary_name": "linux-gcp-fips-headers-5.15.0-1048",
            "binary_version": "5.15.0-1048.56+fips1"
          },
          {
            "binary_name": "linux-gcp-fips-tools-5.15.0-1048",
            "binary_version": "5.15.0-1048.56+fips1"
          },
          {
            "binary_name": "linux-headers-5.15.0-1048-gcp-fips",
            "binary_version": "5.15.0-1048.56+fips1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1048-gcp-fips",
            "binary_version": "5.15.0-1048.56+fips1"
          },
          {
            "binary_name": "linux-image-unsigned-hmac-5.15.0-1048-gcp-fips",
            "binary_version": "5.15.0-1048.56+fips1"
          },
          {
            "binary_name": "linux-modules-5.15.0-1048-gcp-fips",
            "binary_version": "5.15.0-1048.56+fips1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1048-gcp-fips",
            "binary_version": "5.15.0-1048.56+fips1"
          },
          {
            "binary_name": "linux-tools-5.15.0-1048-gcp-fips",
            "binary_version": "5.15.0-1048.56+fips1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:FIPS-preview:22.04:LTS",
        "name": "linux-gcp-fips",
        "purl": "pkg:deb/ubuntu/linux-gcp-fips@5.15.0-1048.56+fips1?arch=source\u0026distro=fips-preview/jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1048.56+fips1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
        "binaries": [
          {
            "binary_name": "linux-aws-fips-cloud-tools-5.15.0-1073",
            "binary_version": "5.15.0-1073.79+fips1"
          },
          {
            "binary_name": "linux-aws-fips-headers-5.15.0-1073",
            "binary_version": "5.15.0-1073.79+fips1"
          },
          {
            "binary_name": "linux-aws-fips-tools-5.15.0-1073",
            "binary_version": "5.15.0-1073.79+fips1"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-1073-aws-fips",
            "binary_version": "5.15.0-1073.79+fips1"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-1073-aws-fips",
            "binary_version": "5.15.0-1073.79+fips1"
          },
          {
            "binary_name": "linux-headers-5.15.0-1073-aws-fips",
            "binary_version": "5.15.0-1073.79+fips1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1073-aws-fips",
            "binary_version": "5.15.0-1073.79+fips1"
          },
          {
            "binary_name": "linux-image-unsigned-hmac-5.15.0-1073-aws-fips",
            "binary_version": "5.15.0-1073.79+fips1"
          },
          {
            "binary_name": "linux-modules-5.15.0-1073-aws-fips",
            "binary_version": "5.15.0-1073.79+fips1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1073-aws-fips",
            "binary_version": "5.15.0-1073.79+fips1"
          },
          {
            "binary_name": "linux-tools-5.15.0-1073-aws-fips",
            "binary_version": "5.15.0-1073.79+fips1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:FIPS-updates:22.04:LTS",
        "name": "linux-aws-fips",
        "purl": "pkg:deb/ubuntu/linux-aws-fips@5.15.0-1073.79+fips1?arch=source\u0026distro=fips-updates/jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1073.79+fips1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1051.56+fips1",
        "5.15.0-1052.57+fips1",
        "5.15.0-1053.58+fips1",
        "5.15.0-1055.60+fips1",
        "5.15.0-1056.61+fips1",
        "5.15.0-1057.63+fips1",
        "5.15.0-1060.66+fips1",
        "5.15.0-1061.67+fips1",
        "5.15.0-1062.68+fips1",
        "5.15.0-1063.69+fips1",
        "5.15.0-1064.70+fips1",
        "5.15.0-1065.71+fips1",
        "5.15.0-1066.72+fips1",
        "5.15.0-1067.73+fips1",
        "5.15.0-1068.74+fips1",
        "5.15.0-1069.75+fips1",
        "5.15.0-1070.76+fips1",
        "5.15.0-1071.77+fips1",
        "5.15.0-1072.78+fips1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
        "binaries": [
          {
            "binary_name": "linux-azure-fips-cloud-tools-5.15.0-1078",
            "binary_version": "5.15.0-1078.87+fips1"
          },
          {
            "binary_name": "linux-azure-fips-headers-5.15.0-1078",
            "binary_version": "5.15.0-1078.87+fips1"
          },
          {
            "binary_name": "linux-azure-fips-tools-5.15.0-1078",
            "binary_version": "5.15.0-1078.87+fips1"
          },
          {
            "binary_name": "linux-buildinfo-5.15.0-1078-azure-fips",
            "binary_version": "5.15.0-1078.87+fips1"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-1078-azure-fips",
            "binary_version": "5.15.0-1078.87+fips1"
          },
          {
            "binary_name": "linux-headers-5.15.0-1078-azure-fips",
            "binary_version": "5.15.0-1078.87+fips1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1078-azure-fips",
            "binary_version": "5.15.0-1078.87+fips1"
          },
          {
            "binary_name": "linux-image-unsigned-hmac-5.15.0-1078-azure-fips",
            "binary_version": "5.15.0-1078.87+fips1"
          },
          {
            "binary_name": "linux-modules-5.15.0-1078-azure-fips",
            "binary_version": "5.15.0-1078.87+fips1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1078-azure-fips",
            "binary_version": "5.15.0-1078.87+fips1"
          },
          {
            "binary_name": "linux-modules-involflt-5.15.0-1078-azure-fips",
            "binary_version": "5.15.0-1078.87+fips1"
          },
          {
            "binary_name": "linux-tools-5.15.0-1078-azure-fips",
            "binary_version": "5.15.0-1078.87+fips1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:FIPS-updates:22.04:LTS",
        "name": "linux-azure-fips",
        "purl": "pkg:deb/ubuntu/linux-azure-fips@5.15.0-1078.87+fips1?arch=source\u0026distro=fips-updates/jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1078.87+fips1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1053.61+fips1",
        "5.15.0-1058.66+fips1",
        "5.15.0-1059.67+fips1",
        "5.15.0-1060.69+fips1",
        "5.15.0-1061.70+fips1",
        "5.15.0-1063.72+fips1",
        "5.15.0-1064.73+fips1",
        "5.15.0-1065.74+fips1",
        "5.15.0-1067.76+fips1",
        "5.15.0-1068.77+fips1",
        "5.15.0-1070.79+fips1",
        "5.15.0-1071.80+fips1",
        "5.15.0-1072.81+fips1",
        "5.15.0-1073.82+fips1",
        "5.15.0-1074.83+fips1",
        "5.15.0-1075.84+fips1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-127-fips",
            "binary_version": "5.15.0-127.137+fips1"
          },
          {
            "binary_name": "linux-fips-headers-5.15.0-127",
            "binary_version": "5.15.0-127.137+fips1"
          },
          {
            "binary_name": "linux-fips-tools-5.15.0-127",
            "binary_version": "5.15.0-127.137+fips1"
          },
          {
            "binary_name": "linux-headers-5.15.0-127-fips",
            "binary_version": "5.15.0-127.137+fips1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-127-fips",
            "binary_version": "5.15.0-127.137+fips1"
          },
          {
            "binary_name": "linux-image-unsigned-hmac-5.15.0-127-fips",
            "binary_version": "5.15.0-127.137+fips1"
          },
          {
            "binary_name": "linux-modules-5.15.0-127-fips",
            "binary_version": "5.15.0-127.137+fips1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-127-fips",
            "binary_version": "5.15.0-127.137+fips1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-5.15.0-127-fips",
            "binary_version": "5.15.0-127.137+fips1"
          },
          {
            "binary_name": "linux-tools-5.15.0-127-fips",
            "binary_version": "5.15.0-127.137+fips1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:FIPS-updates:22.04:LTS",
        "name": "linux-fips",
        "purl": "pkg:deb/ubuntu/linux-fips@5.15.0-127.137+fips1?arch=source\u0026distro=fips-updates/jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-127.137+fips1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-73.80+fips1",
        "5.15.0-92.102+fips1",
        "5.15.0-94.104+fips1",
        "5.15.0-97.107+fips1",
        "5.15.0-100.110+fips1",
        "5.15.0-101.111+fips1",
        "5.15.0-102.112+fips1",
        "5.15.0-105.115+fips1",
        "5.15.0-106.116+fips1",
        "5.15.0-107.117+fips1",
        "5.15.0-111.121+fips1",
        "5.15.0-113.123+fips1",
        "5.15.0-115.125+fips1",
        "5.15.0-117.127+fips1",
        "5.15.0-118.128+fips1",
        "5.15.0-119.129+fips1",
        "5.15.0-121.131+fips1",
        "5.15.0-122.132+fips1",
        "5.15.0-124.134+fips1",
        "5.15.0-125.135+fips1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1072-gcp-fips",
            "binary_version": "5.15.0-1072.80+fips1"
          },
          {
            "binary_name": "linux-gcp-fips-headers-5.15.0-1072",
            "binary_version": "5.15.0-1072.80+fips1"
          },
          {
            "binary_name": "linux-gcp-fips-tools-5.15.0-1072",
            "binary_version": "5.15.0-1072.80+fips1"
          },
          {
            "binary_name": "linux-headers-5.15.0-1072-gcp-fips",
            "binary_version": "5.15.0-1072.80+fips1"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1072-gcp-fips",
            "binary_version": "5.15.0-1072.80+fips1"
          },
          {
            "binary_name": "linux-image-unsigned-hmac-5.15.0-1072-gcp-fips",
            "binary_version": "5.15.0-1072.80+fips1"
          },
          {
            "binary_name": "linux-modules-5.15.0-1072-gcp-fips",
            "binary_version": "5.15.0-1072.80+fips1"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1072-gcp-fips",
            "binary_version": "5.15.0-1072.80+fips1"
          },
          {
            "binary_name": "linux-tools-5.15.0-1072-gcp-fips",
            "binary_version": "5.15.0-1072.80+fips1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:FIPS-updates:22.04:LTS",
        "name": "linux-gcp-fips",
        "purl": "pkg:deb/ubuntu/linux-gcp-fips@5.15.0-1072.80+fips1?arch=source\u0026distro=fips-updates/jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1072.80+fips1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1048.56+fips1",
        "5.15.0-1055.63+fips2",
        "5.15.0-1058.66+fips1",
        "5.15.0-1059.67+fips1",
        "5.15.0-1060.68+fips1",
        "5.15.0-1062.70+fips1",
        "5.15.0-1063.71+fips1",
        "5.15.0-1064.72+fips1",
        "5.15.0-1065.73+fips1",
        "5.15.0-1066.74+fips1",
        "5.15.0-1067.75+fips1",
        "5.15.0-1068.76+fips1",
        "5.15.0-1069.77+fips1",
        "5.15.0-1070.78+fips1",
        "5.15.0-1071.79+fips1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1066-intel-iot-realtime",
            "binary_version": "5.15.0-1066.68"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-1066-intel-iot-realtime",
            "binary_version": "5.15.0-1066.68"
          },
          {
            "binary_name": "linux-headers-5.15.0-1066-intel-iot-realtime",
            "binary_version": "5.15.0-1066.68"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1066-intel-iot-realtime",
            "binary_version": "5.15.0-1066.68"
          },
          {
            "binary_name": "linux-intel-iot-realtime-cloud-tools-5.15.0-1066",
            "binary_version": "5.15.0-1066.68"
          },
          {
            "binary_name": "linux-intel-iot-realtime-cloud-tools-common",
            "binary_version": "5.15.0-1066.68"
          },
          {
            "binary_name": "linux-intel-iot-realtime-headers-5.15.0-1066",
            "binary_version": "5.15.0-1066.68"
          },
          {
            "binary_name": "linux-intel-iot-realtime-tools-5.15.0-1066",
            "binary_version": "5.15.0-1066.68"
          },
          {
            "binary_name": "linux-intel-iot-realtime-tools-common",
            "binary_version": "5.15.0-1066.68"
          },
          {
            "binary_name": "linux-intel-iot-realtime-tools-host",
            "binary_version": "5.15.0-1066.68"
          },
          {
            "binary_name": "linux-modules-5.15.0-1066-intel-iot-realtime",
            "binary_version": "5.15.0-1066.68"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1066-intel-iot-realtime",
            "binary_version": "5.15.0-1066.68"
          },
          {
            "binary_name": "linux-tools-5.15.0-1066-intel-iot-realtime",
            "binary_version": "5.15.0-1066.68"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:Realtime:22.04:LTS",
        "name": "linux-intel-iot-realtime",
        "purl": "pkg:deb/ubuntu/linux-intel-iot-realtime@5.15.0-1066.68?arch=source\u0026distro=realtime/jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1066.68"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1021.26",
        "5.15.0-1022.27",
        "5.15.0-1023.28",
        "5.15.0-1024.29",
        "5.15.0-1028.33",
        "5.15.0-1033.35",
        "5.15.0-1034.36",
        "5.15.0-1035.37",
        "5.15.0-1036.38",
        "5.15.0-1037.39",
        "5.15.0-1038.40",
        "5.15.0-1039.41",
        "5.15.0-1040.42",
        "5.15.0-1041.43",
        "5.15.0-1042.44",
        "5.15.0-1043.45",
        "5.15.0-1044.46",
        "5.15.0-1046.48",
        "5.15.0-1047.49",
        "5.15.0-1048.50",
        "5.15.0-1049.51",
        "5.15.0-1050.52",
        "5.15.0-1053.55",
        "5.15.0-1054.56",
        "5.15.0-1055.57",
        "5.15.0-1056.58",
        "5.15.0-1057.59",
        "5.15.0-1058.60",
        "5.15.0-1059.61",
        "5.15.0-1060.62",
        "5.15.0-1061.63",
        "5.15.0-1063.65",
        "5.15.0-1064.66"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-5.15.0-1074-realtime",
            "binary_version": "5.15.0-1074.82"
          },
          {
            "binary_name": "linux-cloud-tools-5.15.0-1074-realtime",
            "binary_version": "5.15.0-1074.82"
          },
          {
            "binary_name": "linux-headers-5.15.0-1074-realtime",
            "binary_version": "5.15.0-1074.82"
          },
          {
            "binary_name": "linux-image-unsigned-5.15.0-1074-realtime",
            "binary_version": "5.15.0-1074.82"
          },
          {
            "binary_name": "linux-modules-5.15.0-1074-realtime",
            "binary_version": "5.15.0-1074.82"
          },
          {
            "binary_name": "linux-modules-extra-5.15.0-1074-realtime",
            "binary_version": "5.15.0-1074.82"
          },
          {
            "binary_name": "linux-modules-iwlwifi-5.15.0-1074-realtime",
            "binary_version": "5.15.0-1074.82"
          },
          {
            "binary_name": "linux-realtime-cloud-tools-5.15.0-1074",
            "binary_version": "5.15.0-1074.82"
          },
          {
            "binary_name": "linux-realtime-cloud-tools-common",
            "binary_version": "5.15.0-1074.82"
          },
          {
            "binary_name": "linux-realtime-headers-5.15.0-1074",
            "binary_version": "5.15.0-1074.82"
          },
          {
            "binary_name": "linux-realtime-tools-5.15.0-1074",
            "binary_version": "5.15.0-1074.82"
          },
          {
            "binary_name": "linux-realtime-tools-common",
            "binary_version": "5.15.0-1074.82"
          },
          {
            "binary_name": "linux-realtime-tools-host",
            "binary_version": "5.15.0-1074.82"
          },
          {
            "binary_name": "linux-tools-5.15.0-1074-realtime",
            "binary_version": "5.15.0-1074.82"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:Realtime:22.04:LTS",
        "name": "linux-realtime",
        "purl": "pkg:deb/ubuntu/linux-realtime@5.15.0-1074.82?arch=source\u0026distro=realtime/jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.15.0-1074.82"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.15.0-1006.6",
        "5.15.0-1007.7",
        "5.15.0-1009.9",
        "5.15.0-1011.11",
        "5.15.0-1014.14",
        "5.15.0-1015.15",
        "5.15.0-1016.16",
        "5.15.0-1019.19",
        "5.15.0-1020.20",
        "5.15.0-1021.21",
        "5.15.0-1022.22",
        "5.15.0-1024.25",
        "5.15.0-1025.28",
        "5.15.0-1028.31",
        "5.15.0-1029.32",
        "5.15.0-1030.33",
        "5.15.0-1032.35",
        "5.15.0-1033.36",
        "5.15.0-1034.37",
        "5.15.0-1036.39",
        "5.15.0-1037.40",
        "5.15.0-1038.41",
        "5.15.0-1039.42",
        "5.15.0-1040.45",
        "5.15.0-1041.46",
        "5.15.0-1042.47",
        "5.15.0-1043.48",
        "5.15.0-1044.49",
        "5.15.0-1045.50",
        "5.15.0-1046.52",
        "5.15.0-1048.54",
        "5.15.0-1049.55",
        "5.15.0-1050.56",
        "5.15.0-1051.57",
        "5.15.0-1052.58",
        "5.15.0-1053.59",
        "5.15.0-1054.60",
        "5.15.0-1055.62",
        "5.15.0-1056.63",
        "5.15.0-1057.64",
        "5.15.0-1058.66",
        "5.15.0-1061.69",
        "5.15.0-1062.70",
        "5.15.0-1063.71",
        "5.15.0-1064.72",
        "5.15.0-1065.73",
        "5.15.0-1066.74",
        "5.15.0-1067.75",
        "5.15.0-1068.76",
        "5.15.0-1069.77",
        "5.15.0-1070.78",
        "5.15.0-1071.79",
        "5.15.0-1072.80",
        "5.15.0-1073.81"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.1-1018-realtime",
            "binary_version": "6.8.1-1018.19~22.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-6.8.1-1018-realtime",
            "binary_version": "6.8.1-1018.19~22.04.1"
          },
          {
            "binary_name": "linux-headers-6.8.1-1018-realtime",
            "binary_version": "6.8.1-1018.19~22.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.1-1018-realtime",
            "binary_version": "6.8.1-1018.19~22.04.1"
          },
          {
            "binary_name": "linux-modules-6.8.1-1018-realtime",
            "binary_version": "6.8.1-1018.19~22.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.8.1-1018-realtime",
            "binary_version": "6.8.1-1018.19~22.04.1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.8.1-1018-realtime",
            "binary_version": "6.8.1-1018.19~22.04.1"
          },
          {
            "binary_name": "linux-realtime-6.8-cloud-tools-6.8.1-1018",
            "binary_version": "6.8.1-1018.19~22.04.1"
          },
          {
            "binary_name": "linux-realtime-6.8-headers-6.8.1-1018",
            "binary_version": "6.8.1-1018.19~22.04.1"
          },
          {
            "binary_name": "linux-realtime-6.8-tools-6.8.1-1018",
            "binary_version": "6.8.1-1018.19~22.04.1"
          },
          {
            "binary_name": "linux-tools-6.8.1-1018-realtime",
            "binary_version": "6.8.1-1018.19~22.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:Realtime:22.04:LTS",
        "name": "linux-realtime-6.8",
        "purl": "pkg:deb/ubuntu/linux-realtime-6.8@6.8.1-1018.19~22.04.1?arch=source\u0026distro=realtime/jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.1-1018.19~22.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.1-1004.4~22.04.1",
        "6.8.1-1005.5~22.04.2",
        "6.8.1-1006.6~22.04.1",
        "6.8.1-1007.7~22.04.1",
        "6.8.1-1008.8~22.04.1",
        "6.8.1-1009.9~22.04.1",
        "6.8.1-1010.10~22.04.1",
        "6.8.1-1011.11~22.04.1",
        "6.8.1-1012.12~22.04.1",
        "6.8.1-1013.14~22.04.1",
        "6.8.1-1014.15~22.04.1",
        "6.8.1-1015.16~22.04.1",
        "6.8.1-1016.17~22.04.1",
        "6.8.1-1017.18~22.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-buildinfo-6.8.0-56-generic-64k",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-cloud-tools-6.8.0-56",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-cloud-tools-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-cloud-tools-common",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-headers-6.8.0-56",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-headers-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-headers-6.8.0-56-generic-64k",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-image-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-56-generic-64k",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-lib-rust-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-modules-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-modules-6.8.0-56-generic-64k",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-modules-ipu6-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-modules-usbio-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-source-6.8.0",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-tools-6.8.0-56",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-tools-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-tools-6.8.0-56-generic-64k",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-tools-common",
            "binary_version": "6.8.0-56.58"
          },
          {
            "binary_name": "linux-tools-host",
            "binary_version": "6.8.0-56.58"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux",
        "purl": "pkg:deb/ubuntu/linux@6.8.0-56.58?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-56.58"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-9.9",
        "6.6.0-14.14",
        "6.8.0-11.11",
        "6.8.0-20.20",
        "6.8.0-22.22",
        "6.8.0-28.28",
        "6.8.0-31.31",
        "6.8.0-35.35",
        "6.8.0-36.36",
        "6.8.0-38.38",
        "6.8.0-39.39",
        "6.8.0-40.40",
        "6.8.0-41.41",
        "6.8.0-44.44",
        "6.8.0-45.45",
        "6.8.0-47.47",
        "6.8.0-48.48",
        "6.8.0-49.49",
        "6.8.0-50.51",
        "6.8.0-51.52",
        "6.8.0-52.53",
        "6.8.0-53.55",
        "6.8.0-54.56",
        "6.8.0-55.57"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-aws-cloud-tools-6.8.0-1025",
            "binary_version": "6.8.0-1025.27"
          },
          {
            "binary_name": "linux-aws-headers-6.8.0-1025",
            "binary_version": "6.8.0-1025.27"
          },
          {
            "binary_name": "linux-aws-tools-6.8.0-1025",
            "binary_version": "6.8.0-1025.27"
          },
          {
            "binary_name": "linux-buildinfo-6.8.0-1025-aws",
            "binary_version": "6.8.0-1025.27"
          },
          {
            "binary_name": "linux-cloud-tools-6.8.0-1025-aws",
            "binary_version": "6.8.0-1025.27"
          },
          {
            "binary_name": "linux-headers-6.8.0-1025-aws",
            "binary_version": "6.8.0-1025.27"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1025-aws",
            "binary_version": "6.8.0-1025.27"
          },
          {
            "binary_name": "linux-modules-6.8.0-1025-aws",
            "binary_version": "6.8.0-1025.27"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1025-aws",
            "binary_version": "6.8.0-1025.27"
          },
          {
            "binary_name": "linux-tools-6.8.0-1025-aws",
            "binary_version": "6.8.0-1025.27"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-aws",
        "purl": "pkg:deb/ubuntu/linux-aws@6.8.0-1025.27?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1025.27"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-1008.8",
        "6.6.0-1001.1",
        "6.8.0-1001.1",
        "6.8.0-1006.6",
        "6.8.0-1008.8",
        "6.8.0-1009.9",
        "6.8.0-1010.10",
        "6.8.0-1011.12",
        "6.8.0-1012.13",
        "6.8.0-1013.14",
        "6.8.0-1014.15",
        "6.8.0-1015.16",
        "6.8.0-1016.17",
        "6.8.0-1017.18",
        "6.8.0-1018.20",
        "6.8.0-1019.21",
        "6.8.0-1020.22",
        "6.8.0-1021.23",
        "6.8.0-1023.25",
        "6.8.0-1024.26"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-azure-cloud-tools-6.8.0-1025",
            "binary_version": "6.8.0-1025.30"
          },
          {
            "binary_name": "linux-azure-headers-6.8.0-1025",
            "binary_version": "6.8.0-1025.30"
          },
          {
            "binary_name": "linux-azure-tools-6.8.0-1025",
            "binary_version": "6.8.0-1025.30"
          },
          {
            "binary_name": "linux-buildinfo-6.8.0-1025-azure",
            "binary_version": "6.8.0-1025.30"
          },
          {
            "binary_name": "linux-cloud-tools-6.8.0-1025-azure",
            "binary_version": "6.8.0-1025.30"
          },
          {
            "binary_name": "linux-headers-6.8.0-1025-azure",
            "binary_version": "6.8.0-1025.30"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1025-azure",
            "binary_version": "6.8.0-1025.30"
          },
          {
            "binary_name": "linux-modules-6.8.0-1025-azure",
            "binary_version": "6.8.0-1025.30"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1025-azure",
            "binary_version": "6.8.0-1025.30"
          },
          {
            "binary_name": "linux-modules-involflt-6.8.0-1025-azure",
            "binary_version": "6.8.0-1025.30"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.8.0-1025-azure",
            "binary_version": "6.8.0-1025.30"
          },
          {
            "binary_name": "linux-tools-6.8.0-1025-azure",
            "binary_version": "6.8.0-1025.30"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-azure",
        "purl": "pkg:deb/ubuntu/linux-azure@6.8.0-1025.30?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1025.30"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-1007.7",
        "6.6.0-1001.1",
        "6.8.0-1001.1",
        "6.8.0-1005.5",
        "6.8.0-1006.6",
        "6.8.0-1007.7",
        "6.8.0-1008.8",
        "6.8.0-1009.9",
        "6.8.0-1010.10",
        "6.8.0-1012.14",
        "6.8.0-1013.15",
        "6.8.0-1014.16",
        "6.8.0-1015.17",
        "6.8.0-1016.18",
        "6.8.0-1017.20",
        "6.8.0-1018.21",
        "6.8.0-1020.23",
        "6.8.0-1021.25"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-azure-6.11-cloud-tools-6.11.0-1012",
            "binary_version": "6.11.0-1012.12~24.04.1"
          },
          {
            "binary_name": "linux-azure-6.11-headers-6.11.0-1012",
            "binary_version": "6.11.0-1012.12~24.04.1"
          },
          {
            "binary_name": "linux-azure-6.11-tools-6.11.0-1012",
            "binary_version": "6.11.0-1012.12~24.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.11.0-1012-azure",
            "binary_version": "6.11.0-1012.12~24.04.1"
          },
          {
            "binary_name": "linux-cloud-tools-6.11.0-1012-azure",
            "binary_version": "6.11.0-1012.12~24.04.1"
          },
          {
            "binary_name": "linux-headers-6.11.0-1012-azure",
            "binary_version": "6.11.0-1012.12~24.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.11.0-1012-azure",
            "binary_version": "6.11.0-1012.12~24.04.1"
          },
          {
            "binary_name": "linux-modules-6.11.0-1012-azure",
            "binary_version": "6.11.0-1012.12~24.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.11.0-1012-azure",
            "binary_version": "6.11.0-1012.12~24.04.1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.11.0-1012-azure",
            "binary_version": "6.11.0-1012.12~24.04.1"
          },
          {
            "binary_name": "linux-tools-6.11.0-1012-azure",
            "binary_version": "6.11.0-1012.12~24.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-azure-6.11",
        "purl": "pkg:deb/ubuntu/linux-azure-6.11@6.11.0-1012.12~24.04.1?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.11.0-1012.12~24.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.11.0-1008.8~24.04.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-azure-nvidia-cloud-tools-6.8.0-1014",
            "binary_version": "6.8.0-1014.15"
          },
          {
            "binary_name": "linux-azure-nvidia-cloud-tools-common",
            "binary_version": "6.8.0-1014.15"
          },
          {
            "binary_name": "linux-azure-nvidia-headers-6.8.0-1014",
            "binary_version": "6.8.0-1014.15"
          },
          {
            "binary_name": "linux-azure-nvidia-tools-6.8.0-1014",
            "binary_version": "6.8.0-1014.15"
          },
          {
            "binary_name": "linux-buildinfo-6.8.0-1014-azure-nvidia",
            "binary_version": "6.8.0-1014.15"
          },
          {
            "binary_name": "linux-cloud-tools-6.8.0-1014-azure-nvidia",
            "binary_version": "6.8.0-1014.15"
          },
          {
            "binary_name": "linux-headers-6.8.0-1014-azure-nvidia",
            "binary_version": "6.8.0-1014.15"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1014-azure-nvidia",
            "binary_version": "6.8.0-1014.15"
          },
          {
            "binary_name": "linux-modules-6.8.0-1014-azure-nvidia",
            "binary_version": "6.8.0-1014.15"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1014-azure-nvidia",
            "binary_version": "6.8.0-1014.15"
          },
          {
            "binary_name": "linux-tools-6.8.0-1014-azure-nvidia",
            "binary_version": "6.8.0-1014.15"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-azure-nvidia",
        "purl": "pkg:deb/ubuntu/linux-azure-nvidia@6.8.0-1014.15?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1014.15"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-1013.14"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-1026-gcp",
            "binary_version": "6.8.0-1026.28"
          },
          {
            "binary_name": "linux-buildinfo-6.8.0-1026-gcp-64k",
            "binary_version": "6.8.0-1026.28"
          },
          {
            "binary_name": "linux-gcp-headers-6.8.0-1026",
            "binary_version": "6.8.0-1026.28"
          },
          {
            "binary_name": "linux-gcp-tools-6.8.0-1026",
            "binary_version": "6.8.0-1026.28"
          },
          {
            "binary_name": "linux-headers-6.8.0-1026-gcp",
            "binary_version": "6.8.0-1026.28"
          },
          {
            "binary_name": "linux-headers-6.8.0-1026-gcp-64k",
            "binary_version": "6.8.0-1026.28"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1026-gcp",
            "binary_version": "6.8.0-1026.28"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1026-gcp-64k",
            "binary_version": "6.8.0-1026.28"
          },
          {
            "binary_name": "linux-modules-6.8.0-1026-gcp",
            "binary_version": "6.8.0-1026.28"
          },
          {
            "binary_name": "linux-modules-6.8.0-1026-gcp-64k",
            "binary_version": "6.8.0-1026.28"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1026-gcp",
            "binary_version": "6.8.0-1026.28"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1026-gcp-64k",
            "binary_version": "6.8.0-1026.28"
          },
          {
            "binary_name": "linux-tools-6.8.0-1026-gcp",
            "binary_version": "6.8.0-1026.28"
          },
          {
            "binary_name": "linux-tools-6.8.0-1026-gcp-64k",
            "binary_version": "6.8.0-1026.28"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-gcp",
        "purl": "pkg:deb/ubuntu/linux-gcp@6.8.0-1026.28?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1026.28"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-1007.7",
        "6.6.0-1001.1",
        "6.8.0-1002.2",
        "6.8.0-1005.5",
        "6.8.0-1006.6",
        "6.8.0-1007.7",
        "6.8.0-1008.9",
        "6.8.0-1009.10",
        "6.8.0-1010.11",
        "6.8.0-1011.12",
        "6.8.0-1012.13",
        "6.8.0-1013.14",
        "6.8.0-1014.16",
        "6.8.0-1015.17",
        "6.8.0-1016.18",
        "6.8.0-1017.19",
        "6.8.0-1018.20",
        "6.8.0-1019.21",
        "6.8.0-1020.22",
        "6.8.0-1021.23",
        "6.8.0-1024.26",
        "6.8.0-1025.27"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.11.0-1011-gcp",
            "binary_version": "6.11.0-1011.11~24.04.1"
          },
          {
            "binary_name": "linux-buildinfo-6.11.0-1011-gcp-64k",
            "binary_version": "6.11.0-1011.11~24.04.1"
          },
          {
            "binary_name": "linux-gcp-6.11-headers-6.11.0-1011",
            "binary_version": "6.11.0-1011.11~24.04.1"
          },
          {
            "binary_name": "linux-gcp-6.11-lib-rust-6.11.0-1011-gcp",
            "binary_version": "6.11.0-1011.11~24.04.1"
          },
          {
            "binary_name": "linux-gcp-6.11-tools-6.11.0-1011",
            "binary_version": "6.11.0-1011.11~24.04.1"
          },
          {
            "binary_name": "linux-headers-6.11.0-1011-gcp",
            "binary_version": "6.11.0-1011.11~24.04.1"
          },
          {
            "binary_name": "linux-headers-6.11.0-1011-gcp-64k",
            "binary_version": "6.11.0-1011.11~24.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.11.0-1011-gcp",
            "binary_version": "6.11.0-1011.11~24.04.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.11.0-1011-gcp-64k",
            "binary_version": "6.11.0-1011.11~24.04.1"
          },
          {
            "binary_name": "linux-modules-6.11.0-1011-gcp",
            "binary_version": "6.11.0-1011.11~24.04.1"
          },
          {
            "binary_name": "linux-modules-6.11.0-1011-gcp-64k",
            "binary_version": "6.11.0-1011.11~24.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.11.0-1011-gcp",
            "binary_version": "6.11.0-1011.11~24.04.1"
          },
          {
            "binary_name": "linux-modules-extra-6.11.0-1011-gcp-64k",
            "binary_version": "6.11.0-1011.11~24.04.1"
          },
          {
            "binary_name": "linux-tools-6.11.0-1011-gcp",
            "binary_version": "6.11.0-1011.11~24.04.1"
          },
          {
            "binary_name": "linux-tools-6.11.0-1011-gcp-64k",
            "binary_version": "6.11.0-1011.11~24.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-gcp-6.11",
        "purl": "pkg:deb/ubuntu/linux-gcp-6.11@6.11.0-1011.11~24.04.1?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.11.0-1011.11~24.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.11.0-1006.6~24.04.2"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-1021-gke",
            "binary_version": "6.8.0-1021.25"
          },
          {
            "binary_name": "linux-gke-headers-6.8.0-1021",
            "binary_version": "6.8.0-1021.25"
          },
          {
            "binary_name": "linux-gke-tools-6.8.0-1021",
            "binary_version": "6.8.0-1021.25"
          },
          {
            "binary_name": "linux-headers-6.8.0-1021-gke",
            "binary_version": "6.8.0-1021.25"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1021-gke",
            "binary_version": "6.8.0-1021.25"
          },
          {
            "binary_name": "linux-modules-6.8.0-1021-gke",
            "binary_version": "6.8.0-1021.25"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1021-gke",
            "binary_version": "6.8.0-1021.25"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.8.0-1021-gke",
            "binary_version": "6.8.0-1021.25"
          },
          {
            "binary_name": "linux-tools-6.8.0-1021-gke",
            "binary_version": "6.8.0-1021.25"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-gke",
        "purl": "pkg:deb/ubuntu/linux-gke@6.8.0-1021.25?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1021.25"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-1003.5",
        "6.8.0-1004.7",
        "6.8.0-1005.8",
        "6.8.0-1006.9",
        "6.8.0-1007.10",
        "6.8.0-1008.11",
        "6.8.0-1009.12",
        "6.8.0-1010.13",
        "6.8.0-1011.14",
        "6.8.0-1012.15",
        "6.8.0-1013.17",
        "6.8.0-1014.18",
        "6.8.0-1015.19",
        "6.8.0-1016.20",
        "6.8.0-1017.21",
        "6.8.0-1019.23",
        "6.8.0-1020.24"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-1008-gkeop",
            "binary_version": "6.8.0-1008.10"
          },
          {
            "binary_name": "linux-cloud-tools-6.8.0-1008-gkeop",
            "binary_version": "6.8.0-1008.10"
          },
          {
            "binary_name": "linux-gkeop-cloud-tools-6.8.0-1008",
            "binary_version": "6.8.0-1008.10"
          },
          {
            "binary_name": "linux-gkeop-headers-6.8.0-1008",
            "binary_version": "6.8.0-1008.10"
          },
          {
            "binary_name": "linux-gkeop-tools-6.8.0-1008",
            "binary_version": "6.8.0-1008.10"
          },
          {
            "binary_name": "linux-headers-6.8.0-1008-gkeop",
            "binary_version": "6.8.0-1008.10"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1008-gkeop",
            "binary_version": "6.8.0-1008.10"
          },
          {
            "binary_name": "linux-modules-6.8.0-1008-gkeop",
            "binary_version": "6.8.0-1008.10"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1008-gkeop",
            "binary_version": "6.8.0-1008.10"
          },
          {
            "binary_name": "linux-tools-6.8.0-1008-gkeop",
            "binary_version": "6.8.0-1008.10"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-gkeop",
        "purl": "pkg:deb/ubuntu/linux-gkeop@6.8.0-1008.10?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1008.10"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-1001.3",
        "6.8.0-1002.4",
        "6.8.0-1003.5",
        "6.8.0-1004.6",
        "6.8.0-1006.8",
        "6.8.0-1007.9"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-1022-ibm",
            "binary_version": "6.8.0-1022.22"
          },
          {
            "binary_name": "linux-headers-6.8.0-1022-ibm",
            "binary_version": "6.8.0-1022.22"
          },
          {
            "binary_name": "linux-ibm-headers-6.8.0-1022",
            "binary_version": "6.8.0-1022.22"
          },
          {
            "binary_name": "linux-ibm-tools-6.8.0-1022",
            "binary_version": "6.8.0-1022.22"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1022-ibm",
            "binary_version": "6.8.0-1022.22"
          },
          {
            "binary_name": "linux-modules-6.8.0-1022-ibm",
            "binary_version": "6.8.0-1022.22"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1022-ibm",
            "binary_version": "6.8.0-1022.22"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.8.0-1022-ibm",
            "binary_version": "6.8.0-1022.22"
          },
          {
            "binary_name": "linux-tools-6.8.0-1022-ibm",
            "binary_version": "6.8.0-1022.22"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-ibm",
        "purl": "pkg:deb/ubuntu/linux-ibm@6.8.0-1022.22?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1022.22"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-1009.9",
        "6.8.0-1001.1",
        "6.8.0-1003.3",
        "6.8.0-1004.4",
        "6.8.0-1005.5",
        "6.8.0-1006.6",
        "6.8.0-1007.7",
        "6.8.0-1008.8",
        "6.8.0-1009.9",
        "6.8.0-1010.10",
        "6.8.0-1011.11",
        "6.8.0-1012.12",
        "6.8.0-1013.13",
        "6.8.0-1014.14",
        "6.8.0-1015.15",
        "6.8.0-1016.16",
        "6.8.0-1017.17",
        "6.8.0-1018.18",
        "6.8.0-1019.19"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-56-lowlatency",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-buildinfo-6.8.0-56-lowlatency-64k",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-cloud-tools-6.8.0-56-lowlatency",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-56-lowlatency",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-56-lowlatency-64k",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-56-lowlatency",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-56-lowlatency-64k",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-lowlatency-cloud-tools-6.8.0-56",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-lowlatency-headers-6.8.0-56",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-lowlatency-lib-rust-6.8.0-56-lowlatency",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-lowlatency-tools-6.8.0-56",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-56-lowlatency",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-56-lowlatency-64k",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.8.0-56-lowlatency",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-56-lowlatency",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-56-lowlatency-64k",
            "binary_version": "6.8.0-56.58.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-lowlatency",
        "purl": "pkg:deb/ubuntu/linux-lowlatency@6.8.0-56.58.1?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-56.58.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-9.9.1",
        "6.6.0-14.14.1",
        "6.8.0-7.7.1",
        "6.8.0-25.25.3",
        "6.8.0-28.28.1",
        "6.8.0-31.31.1",
        "6.8.0-35.35.1",
        "6.8.0-36.36.1",
        "6.8.0-38.38.1",
        "6.8.0-39.39.1",
        "6.8.0-40.40.1",
        "6.8.0-41.41.1",
        "6.8.0-44.44.1",
        "6.8.0-45.45.1",
        "6.8.0-47.47.1",
        "6.8.0-48.48.3",
        "6.8.0-49.49.1",
        "6.8.0-50.51.1",
        "6.8.0-51.52.1",
        "6.8.0-52.53.1",
        "6.8.0-53.55.2",
        "6.8.0-54.56.1",
        "6.8.0-55.57.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-1024-nvidia",
            "binary_version": "6.8.0-1024.27"
          },
          {
            "binary_name": "linux-buildinfo-6.8.0-1024-nvidia-64k",
            "binary_version": "6.8.0-1024.27"
          },
          {
            "binary_name": "linux-headers-6.8.0-1024-nvidia",
            "binary_version": "6.8.0-1024.27"
          },
          {
            "binary_name": "linux-headers-6.8.0-1024-nvidia-64k",
            "binary_version": "6.8.0-1024.27"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1024-nvidia",
            "binary_version": "6.8.0-1024.27"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1024-nvidia-64k",
            "binary_version": "6.8.0-1024.27"
          },
          {
            "binary_name": "linux-modules-6.8.0-1024-nvidia",
            "binary_version": "6.8.0-1024.27"
          },
          {
            "binary_name": "linux-modules-6.8.0-1024-nvidia-64k",
            "binary_version": "6.8.0-1024.27"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1024-nvidia",
            "binary_version": "6.8.0-1024.27"
          },
          {
            "binary_name": "linux-modules-nvidia-fs-6.8.0-1024-nvidia",
            "binary_version": "6.8.0-1024.27"
          },
          {
            "binary_name": "linux-modules-nvidia-fs-6.8.0-1024-nvidia-64k",
            "binary_version": "6.8.0-1024.27"
          },
          {
            "binary_name": "linux-nvidia-headers-6.8.0-1024",
            "binary_version": "6.8.0-1024.27"
          },
          {
            "binary_name": "linux-nvidia-tools-6.8.0-1024",
            "binary_version": "6.8.0-1024.27"
          },
          {
            "binary_name": "linux-tools-6.8.0-1024-nvidia",
            "binary_version": "6.8.0-1024.27"
          },
          {
            "binary_name": "linux-tools-6.8.0-1024-nvidia-64k",
            "binary_version": "6.8.0-1024.27"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-nvidia",
        "purl": "pkg:deb/ubuntu/linux-nvidia@6.8.0-1024.27?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1024.27"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-1007.7",
        "6.8.0-1008.8",
        "6.8.0-1009.9",
        "6.8.0-1010.10",
        "6.8.0-1011.11",
        "6.8.0-1012.12",
        "6.8.0-1013.14",
        "6.8.0-1014.15",
        "6.8.0-1015.16",
        "6.8.0-1017.19",
        "6.8.0-1018.20",
        "6.8.0-1019.21",
        "6.8.0-1020.22",
        "6.8.0-1021.23",
        "6.8.0-1022.25",
        "6.8.0-1023.26"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.11.0-1007-nvidia",
            "binary_version": "6.11.0-1007.7"
          },
          {
            "binary_name": "linux-buildinfo-6.11.0-1007-nvidia-64k",
            "binary_version": "6.11.0-1007.7"
          },
          {
            "binary_name": "linux-headers-6.11.0-1007-nvidia",
            "binary_version": "6.11.0-1007.7"
          },
          {
            "binary_name": "linux-headers-6.11.0-1007-nvidia-64k",
            "binary_version": "6.11.0-1007.7"
          },
          {
            "binary_name": "linux-image-unsigned-6.11.0-1007-nvidia",
            "binary_version": "6.11.0-1007.7"
          },
          {
            "binary_name": "linux-image-unsigned-6.11.0-1007-nvidia-64k",
            "binary_version": "6.11.0-1007.7"
          },
          {
            "binary_name": "linux-modules-6.11.0-1007-nvidia",
            "binary_version": "6.11.0-1007.7"
          },
          {
            "binary_name": "linux-modules-6.11.0-1007-nvidia-64k",
            "binary_version": "6.11.0-1007.7"
          },
          {
            "binary_name": "linux-modules-extra-6.11.0-1007-nvidia",
            "binary_version": "6.11.0-1007.7"
          },
          {
            "binary_name": "linux-modules-extra-6.11.0-1007-nvidia-64k",
            "binary_version": "6.11.0-1007.7"
          },
          {
            "binary_name": "linux-modules-nvidia-fs-6.11.0-1007-nvidia",
            "binary_version": "6.11.0-1007.7"
          },
          {
            "binary_name": "linux-modules-nvidia-fs-6.11.0-1007-nvidia-64k",
            "binary_version": "6.11.0-1007.7"
          },
          {
            "binary_name": "linux-nvidia-6.11-headers-6.11.0-1007",
            "binary_version": "6.11.0-1007.7"
          },
          {
            "binary_name": "linux-nvidia-6.11-lib-rust-6.11.0-1007-nvidia",
            "binary_version": "6.11.0-1007.7"
          },
          {
            "binary_name": "linux-nvidia-6.11-tools-6.11.0-1007",
            "binary_version": "6.11.0-1007.7"
          },
          {
            "binary_name": "linux-tools-6.11.0-1007-nvidia",
            "binary_version": "6.11.0-1007.7"
          },
          {
            "binary_name": "linux-tools-6.11.0-1007-nvidia-64k",
            "binary_version": "6.11.0-1007.7"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-nvidia-6.11",
        "purl": "pkg:deb/ubuntu/linux-nvidia-6.11@6.11.0-1007.7?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.11.0-1007.7"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.11.0-1002.2",
        "6.11.0-1003.3"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-1024-nvidia-lowlatency",
            "binary_version": "6.8.0-1024.27.1"
          },
          {
            "binary_name": "linux-buildinfo-6.8.0-1024-nvidia-lowlatency-64k",
            "binary_version": "6.8.0-1024.27.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-1024-nvidia-lowlatency",
            "binary_version": "6.8.0-1024.27.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-1024-nvidia-lowlatency-64k",
            "binary_version": "6.8.0-1024.27.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1024-nvidia-lowlatency",
            "binary_version": "6.8.0-1024.27.1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1024-nvidia-lowlatency-64k",
            "binary_version": "6.8.0-1024.27.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-1024-nvidia-lowlatency",
            "binary_version": "6.8.0-1024.27.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-1024-nvidia-lowlatency-64k",
            "binary_version": "6.8.0-1024.27.1"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1024-nvidia-lowlatency",
            "binary_version": "6.8.0-1024.27.1"
          },
          {
            "binary_name": "linux-modules-nvidia-fs-6.8.0-1024-nvidia-lowlatency",
            "binary_version": "6.8.0-1024.27.1"
          },
          {
            "binary_name": "linux-modules-nvidia-fs-6.8.0-1024-nvidia-lowlatency-64k",
            "binary_version": "6.8.0-1024.27.1"
          },
          {
            "binary_name": "linux-nvidia-lowlatency-headers-6.8.0-1024",
            "binary_version": "6.8.0-1024.27.1"
          },
          {
            "binary_name": "linux-nvidia-lowlatency-tools-6.8.0-1024",
            "binary_version": "6.8.0-1024.27.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-1024-nvidia-lowlatency",
            "binary_version": "6.8.0-1024.27.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-1024-nvidia-lowlatency-64k",
            "binary_version": "6.8.0-1024.27.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-nvidia-lowlatency",
        "purl": "pkg:deb/ubuntu/linux-nvidia-lowlatency@6.8.0-1024.27.1?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1024.27.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-1009.9.1",
        "6.8.0-1011.11.1",
        "6.8.0-1012.12.1",
        "6.8.0-1013.14.1",
        "6.8.0-1014.15.1",
        "6.8.0-1015.16.1",
        "6.8.0-1017.19.1",
        "6.8.0-1018.20.1",
        "6.8.0-1019.21.1",
        "6.8.0-1020.22.1",
        "6.8.0-1021.23.1",
        "6.8.0-1022.25.2",
        "6.8.0-1023.26.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-1004-nvidia-tegra",
            "binary_version": "6.8.0-1004.4"
          },
          {
            "binary_name": "linux-buildinfo-6.8.0-1004-nvidia-tegra-rt",
            "binary_version": "6.8.0-1004.4"
          },
          {
            "binary_name": "linux-headers-6.8.0-1004-nvidia-tegra",
            "binary_version": "6.8.0-1004.4"
          },
          {
            "binary_name": "linux-headers-6.8.0-1004-nvidia-tegra-rt",
            "binary_version": "6.8.0-1004.4"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1004-nvidia-tegra",
            "binary_version": "6.8.0-1004.4"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1004-nvidia-tegra-rt",
            "binary_version": "6.8.0-1004.4"
          },
          {
            "binary_name": "linux-modules-6.8.0-1004-nvidia-tegra",
            "binary_version": "6.8.0-1004.4"
          },
          {
            "binary_name": "linux-modules-6.8.0-1004-nvidia-tegra-rt",
            "binary_version": "6.8.0-1004.4"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1004-nvidia-tegra",
            "binary_version": "6.8.0-1004.4"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1004-nvidia-tegra-rt",
            "binary_version": "6.8.0-1004.4"
          },
          {
            "binary_name": "linux-nvidia-tegra-headers-6.8.0-1004",
            "binary_version": "6.8.0-1004.4"
          },
          {
            "binary_name": "linux-nvidia-tegra-tools-6.8.0-1004",
            "binary_version": "6.8.0-1004.4"
          },
          {
            "binary_name": "linux-tools-6.8.0-1004-nvidia-tegra",
            "binary_version": "6.8.0-1004.4"
          },
          {
            "binary_name": "linux-tools-6.8.0-1004-nvidia-tegra-rt",
            "binary_version": "6.8.0-1004.4"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-nvidia-tegra",
        "purl": "pkg:deb/ubuntu/linux-nvidia-tegra@6.8.0-1004.4?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1004.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-1003.3"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.11.0-1015-oem",
            "binary_version": "6.11.0-1015.15"
          },
          {
            "binary_name": "linux-headers-6.11.0-1015-oem",
            "binary_version": "6.11.0-1015.15"
          },
          {
            "binary_name": "linux-image-unsigned-6.11.0-1015-oem",
            "binary_version": "6.11.0-1015.15"
          },
          {
            "binary_name": "linux-modules-6.11.0-1015-oem",
            "binary_version": "6.11.0-1015.15"
          },
          {
            "binary_name": "linux-modules-ipu6-6.11.0-1015-oem",
            "binary_version": "6.11.0-1015.15"
          },
          {
            "binary_name": "linux-modules-ipu7-6.11.0-1015-oem",
            "binary_version": "6.11.0-1015.15"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.11.0-1015-oem",
            "binary_version": "6.11.0-1015.15"
          },
          {
            "binary_name": "linux-modules-usbio-6.11.0-1015-oem",
            "binary_version": "6.11.0-1015.15"
          },
          {
            "binary_name": "linux-modules-vision-6.11.0-1015-oem",
            "binary_version": "6.11.0-1015.15"
          },
          {
            "binary_name": "linux-oem-6.11-headers-6.11.0-1015",
            "binary_version": "6.11.0-1015.15"
          },
          {
            "binary_name": "linux-oem-6.11-tools-6.11.0-1015",
            "binary_version": "6.11.0-1015.15"
          },
          {
            "binary_name": "linux-tools-6.11.0-1015-oem",
            "binary_version": "6.11.0-1015.15"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-oem-6.11",
        "purl": "pkg:deb/ubuntu/linux-oem-6.11@6.11.0-1015.15?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.11.0-1015.15"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.11.0-1007.7",
        "6.11.0-1008.8",
        "6.11.0-1009.9",
        "6.11.0-1010.10",
        "6.11.0-1011.11",
        "6.11.0-1012.12",
        "6.11.0-1013.13"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-1024-oem",
            "binary_version": "6.8.0-1024.24"
          },
          {
            "binary_name": "linux-headers-6.8.0-1024-oem",
            "binary_version": "6.8.0-1024.24"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1024-oem",
            "binary_version": "6.8.0-1024.24"
          },
          {
            "binary_name": "linux-modules-6.8.0-1024-oem",
            "binary_version": "6.8.0-1024.24"
          },
          {
            "binary_name": "linux-modules-ipu6-6.8.0-1024-oem",
            "binary_version": "6.8.0-1024.24"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.8.0-1024-oem",
            "binary_version": "6.8.0-1024.24"
          },
          {
            "binary_name": "linux-modules-usbio-6.8.0-1024-oem",
            "binary_version": "6.8.0-1024.24"
          },
          {
            "binary_name": "linux-oem-6.8-headers-6.8.0-1024",
            "binary_version": "6.8.0-1024.24"
          },
          {
            "binary_name": "linux-oem-6.8-tools-6.8.0-1024",
            "binary_version": "6.8.0-1024.24"
          },
          {
            "binary_name": "linux-tools-6.8.0-1024-oem",
            "binary_version": "6.8.0-1024.24"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-oem-6.8",
        "purl": "pkg:deb/ubuntu/linux-oem-6.8@6.8.0-1024.24?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1024.24"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-1003.3",
        "6.8.0-1004.4",
        "6.8.0-1005.5",
        "6.8.0-1006.6",
        "6.8.0-1007.7",
        "6.8.0-1008.8",
        "6.8.0-1009.9",
        "6.8.0-1010.10",
        "6.8.0-1011.11",
        "6.8.0-1012.12",
        "6.8.0-1013.13",
        "6.8.0-1014.14",
        "6.8.0-1016.16",
        "6.8.0-1017.17",
        "6.8.0-1018.18",
        "6.8.0-1019.19",
        "6.8.0-1020.20"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-1022-oracle",
            "binary_version": "6.8.0-1022.23"
          },
          {
            "binary_name": "linux-buildinfo-6.8.0-1022-oracle-64k",
            "binary_version": "6.8.0-1022.23"
          },
          {
            "binary_name": "linux-headers-6.8.0-1022-oracle",
            "binary_version": "6.8.0-1022.23"
          },
          {
            "binary_name": "linux-headers-6.8.0-1022-oracle-64k",
            "binary_version": "6.8.0-1022.23"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1022-oracle",
            "binary_version": "6.8.0-1022.23"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-1022-oracle-64k",
            "binary_version": "6.8.0-1022.23"
          },
          {
            "binary_name": "linux-modules-6.8.0-1022-oracle",
            "binary_version": "6.8.0-1022.23"
          },
          {
            "binary_name": "linux-modules-6.8.0-1022-oracle-64k",
            "binary_version": "6.8.0-1022.23"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1022-oracle",
            "binary_version": "6.8.0-1022.23"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-1022-oracle-64k",
            "binary_version": "6.8.0-1022.23"
          },
          {
            "binary_name": "linux-oracle-headers-6.8.0-1022",
            "binary_version": "6.8.0-1022.23"
          },
          {
            "binary_name": "linux-oracle-tools-6.8.0-1022",
            "binary_version": "6.8.0-1022.23"
          },
          {
            "binary_name": "linux-tools-6.8.0-1022-oracle",
            "binary_version": "6.8.0-1022.23"
          },
          {
            "binary_name": "linux-tools-6.8.0-1022-oracle-64k",
            "binary_version": "6.8.0-1022.23"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-oracle",
        "purl": "pkg:deb/ubuntu/linux-oracle@6.8.0-1022.23?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1022.23"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-1010.10",
        "6.6.0-1001.1",
        "6.8.0-1001.1",
        "6.8.0-1004.4",
        "6.8.0-1005.5",
        "6.8.0-1006.6",
        "6.8.0-1008.8",
        "6.8.0-1010.10",
        "6.8.0-1011.11",
        "6.8.0-1012.12",
        "6.8.0-1013.13",
        "6.8.0-1014.14",
        "6.8.0-1015.16",
        "6.8.0-1016.17",
        "6.8.0-1017.18",
        "6.8.0-1018.19",
        "6.8.0-1019.20",
        "6.8.0-1020.21",
        "6.8.0-1021.22"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-1028-raspi",
            "binary_version": "6.8.0-1028.32"
          },
          {
            "binary_name": "linux-headers-6.8.0-1028-raspi",
            "binary_version": "6.8.0-1028.32"
          },
          {
            "binary_name": "linux-image-6.8.0-1028-raspi",
            "binary_version": "6.8.0-1028.32"
          },
          {
            "binary_name": "linux-modules-6.8.0-1028-raspi",
            "binary_version": "6.8.0-1028.32"
          },
          {
            "binary_name": "linux-raspi-headers-6.8.0-1028",
            "binary_version": "6.8.0-1028.32"
          },
          {
            "binary_name": "linux-raspi-tools-6.8.0-1028",
            "binary_version": "6.8.0-1028.32"
          },
          {
            "binary_name": "linux-tools-6.8.0-1028-raspi",
            "binary_version": "6.8.0-1028.32"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-raspi",
        "purl": "pkg:deb/ubuntu/linux-raspi@6.8.0-1028.32?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1028.32"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-1005.7",
        "6.7.0-1001.1",
        "6.8.0-1001.1",
        "6.8.0-1002.2",
        "6.8.0-1003.3",
        "6.8.0-1004.4",
        "6.8.0-1005.5",
        "6.8.0-1006.6",
        "6.8.0-1007.7",
        "6.8.0-1008.8",
        "6.8.0-1009.10",
        "6.8.0-1010.11",
        "6.8.0-1011.12",
        "6.8.0-1012.13",
        "6.8.0-1013.14",
        "6.8.0-1014.16",
        "6.8.0-1015.17",
        "6.8.0-1016.18",
        "6.8.0-1017.19",
        "6.8.0-1018.20",
        "6.8.0-1019.23",
        "6.8.0-1020.24",
        "6.8.0-1024.28"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-2019-raspi-realtime",
            "binary_version": "6.8.0-2019.20"
          },
          {
            "binary_name": "linux-headers-6.8.0-2019-raspi-realtime",
            "binary_version": "6.8.0-2019.20"
          },
          {
            "binary_name": "linux-image-6.8.0-2019-raspi-realtime",
            "binary_version": "6.8.0-2019.20"
          },
          {
            "binary_name": "linux-modules-6.8.0-2019-raspi-realtime",
            "binary_version": "6.8.0-2019.20"
          },
          {
            "binary_name": "linux-raspi-realtime-headers-6.8.0-2019",
            "binary_version": "6.8.0-2019.20"
          },
          {
            "binary_name": "linux-raspi-realtime-tools-6.8.0-2019",
            "binary_version": "6.8.0-2019.20"
          },
          {
            "binary_name": "linux-tools-6.8.0-2019-raspi-realtime",
            "binary_version": "6.8.0-2019.20"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-raspi-realtime",
        "purl": "pkg:deb/ubuntu/linux-raspi-realtime@6.8.0-2019.20?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-2019.20"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.1-1015-realtime",
            "binary_version": "6.8.1-1015.16"
          },
          {
            "binary_name": "linux-cloud-tools-6.8.1-1015-realtime",
            "binary_version": "6.8.1-1015.16"
          },
          {
            "binary_name": "linux-headers-6.8.1-1015-realtime",
            "binary_version": "6.8.1-1015.16"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.1-1015-realtime",
            "binary_version": "6.8.1-1015.16"
          },
          {
            "binary_name": "linux-modules-6.8.1-1015-realtime",
            "binary_version": "6.8.1-1015.16"
          },
          {
            "binary_name": "linux-modules-extra-6.8.1-1015-realtime",
            "binary_version": "6.8.1-1015.16"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.8.1-1015-realtime",
            "binary_version": "6.8.1-1015.16"
          },
          {
            "binary_name": "linux-realtime-cloud-tools-6.8.1-1015",
            "binary_version": "6.8.1-1015.16"
          },
          {
            "binary_name": "linux-realtime-headers-6.8.1-1015",
            "binary_version": "6.8.1-1015.16"
          },
          {
            "binary_name": "linux-realtime-tools-6.8.1-1015",
            "binary_version": "6.8.1-1015.16"
          },
          {
            "binary_name": "linux-tools-6.8.1-1015-realtime",
            "binary_version": "6.8.1-1015.16"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-realtime",
        "purl": "pkg:deb/ubuntu/linux-realtime@6.8.1-1015.16?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.1-1015.16"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-headers-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-image-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-modules-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-riscv-headers-6.8.0-56",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-riscv-tools-6.8.0-56",
            "binary_version": "6.8.0-56.58.1"
          },
          {
            "binary_name": "linux-tools-6.8.0-56-generic",
            "binary_version": "6.8.0-56.58.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-riscv",
        "purl": "pkg:deb/ubuntu/linux-riscv@6.8.0-56.58.1?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-56.58.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.5.0-9.9.1",
        "6.8.0-20.20.1",
        "6.8.0-28.28.1",
        "6.8.0-31.31.1",
        "6.8.0-35.35.1",
        "6.8.0-36.36.1",
        "6.8.0-38.38.1",
        "6.8.0-39.39.1",
        "6.8.0-40.40.1",
        "6.8.0-41.41.1",
        "6.8.0-44.44.1",
        "6.8.0-47.47.1",
        "6.8.0-48.48.1",
        "6.8.0-49.49.1",
        "6.8.0-50.51.1",
        "6.8.0-51.52.1",
        "6.8.0-52.53.1",
        "6.8.0-53.55.1",
        "6.8.0-55.57.1"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-1017-xilinx",
            "binary_version": "6.8.0-1017.18"
          },
          {
            "binary_name": "linux-headers-6.8.0-1017-xilinx",
            "binary_version": "6.8.0-1017.18"
          },
          {
            "binary_name": "linux-image-6.8.0-1017-xilinx",
            "binary_version": "6.8.0-1017.18"
          },
          {
            "binary_name": "linux-modules-6.8.0-1017-xilinx",
            "binary_version": "6.8.0-1017.18"
          },
          {
            "binary_name": "linux-tools-6.8.0-1017-xilinx",
            "binary_version": "6.8.0-1017.18"
          },
          {
            "binary_name": "linux-xilinx-headers-6.8.0-1017",
            "binary_version": "6.8.0-1017.18"
          },
          {
            "binary_name": "linux-xilinx-tools-6.8.0-1017",
            "binary_version": "6.8.0-1017.18"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "linux-xilinx",
        "purl": "pkg:deb/ubuntu/linux-xilinx@6.8.0-1017.18?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-1017.18"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-1008.9",
        "6.8.0-1009.10",
        "6.8.0-1011.12",
        "6.8.0-1012.13",
        "6.8.0-1013.14",
        "6.8.0-1014.15",
        "6.8.0-1015.16"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-78-fips",
            "binary_version": "6.8.0-78.78+fips1"
          },
          {
            "binary_name": "linux-fips-headers-6.8.0-78",
            "binary_version": "6.8.0-78.78+fips1"
          },
          {
            "binary_name": "linux-fips-lib-rust-6.8.0-78-fips",
            "binary_version": "6.8.0-78.78+fips1"
          },
          {
            "binary_name": "linux-fips-tools-6.8.0-78",
            "binary_version": "6.8.0-78.78+fips1"
          },
          {
            "binary_name": "linux-headers-6.8.0-78-fips",
            "binary_version": "6.8.0-78.78+fips1"
          },
          {
            "binary_name": "linux-image-6.8.0-78-fips",
            "binary_version": "6.8.0-78.78+fips1"
          },
          {
            "binary_name": "linux-image-hmac-6.8.0-78-fips",
            "binary_version": "6.8.0-78.78+fips1"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.0-78-fips",
            "binary_version": "6.8.0-78.78+fips1"
          },
          {
            "binary_name": "linux-image-unsigned-hmac-6.8.0-78-fips",
            "binary_version": "6.8.0-78.78+fips1"
          },
          {
            "binary_name": "linux-modules-6.8.0-78-fips",
            "binary_version": "6.8.0-78.78+fips1"
          },
          {
            "binary_name": "linux-modules-extra-6.8.0-78-fips",
            "binary_version": "6.8.0-78.78+fips1"
          },
          {
            "binary_name": "linux-modules-ipu6-6.8.0-78-fips",
            "binary_version": "6.8.0-78.78+fips1"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.8.0-78-fips",
            "binary_version": "6.8.0-78.78+fips1"
          },
          {
            "binary_name": "linux-modules-usbio-6.8.0-78-fips",
            "binary_version": "6.8.0-78.78+fips1"
          },
          {
            "binary_name": "linux-tools-6.8.0-78-fips",
            "binary_version": "6.8.0-78.78+fips1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:FIPS-updates:24.04:LTS",
        "name": "linux-fips",
        "purl": "pkg:deb/ubuntu/linux-fips@6.8.0-78.78+fips1?arch=source\u0026distro=fips-updates/noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-78.78+fips1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-38.38+fips4"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.0-2023-raspi-realtime",
            "binary_version": "6.8.0-2023.24"
          },
          {
            "binary_name": "linux-headers-6.8.0-2023-raspi-realtime",
            "binary_version": "6.8.0-2023.24"
          },
          {
            "binary_name": "linux-image-6.8.0-2023-raspi-realtime",
            "binary_version": "6.8.0-2023.24"
          },
          {
            "binary_name": "linux-modules-6.8.0-2023-raspi-realtime",
            "binary_version": "6.8.0-2023.24"
          },
          {
            "binary_name": "linux-raspi-realtime-headers-6.8.0-2023",
            "binary_version": "6.8.0-2023.24"
          },
          {
            "binary_name": "linux-raspi-realtime-tools-6.8.0-2023",
            "binary_version": "6.8.0-2023.24"
          },
          {
            "binary_name": "linux-tools-6.8.0-2023-raspi-realtime",
            "binary_version": "6.8.0-2023.24"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:Realtime:24.04:LTS",
        "name": "linux-raspi-realtime",
        "purl": "pkg:deb/ubuntu/linux-raspi-realtime@6.8.0-2023.24?arch=source\u0026distro=realtime/noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.0-2023.24"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.7.0-2001.1",
        "6.8.0-2001.1",
        "6.8.0-2002.2",
        "6.8.0-2004.4",
        "6.8.0-2005.5",
        "6.8.0-2006.6",
        "6.8.0-2007.7",
        "6.8.0-2008.8",
        "6.8.0-2009.9",
        "6.8.0-2010.10",
        "6.8.0-2011.11",
        "6.8.0-2012.12",
        "6.8.0-2013.14",
        "6.8.0-2014.15",
        "6.8.0-2015.16",
        "6.8.0-2016.17",
        "6.8.0-2017.18",
        "6.8.0-2018.19",
        "6.8.0-2019.20",
        "6.8.0-2022.23"
      ]
    },
    {
      "ecosystem_specific": {
        "availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
        "binaries": [
          {
            "binary_name": "linux-buildinfo-6.8.1-1018-realtime",
            "binary_version": "6.8.1-1018.19"
          },
          {
            "binary_name": "linux-cloud-tools-6.8.1-1018-realtime",
            "binary_version": "6.8.1-1018.19"
          },
          {
            "binary_name": "linux-headers-6.8.1-1018-realtime",
            "binary_version": "6.8.1-1018.19"
          },
          {
            "binary_name": "linux-image-unsigned-6.8.1-1018-realtime",
            "binary_version": "6.8.1-1018.19"
          },
          {
            "binary_name": "linux-modules-6.8.1-1018-realtime",
            "binary_version": "6.8.1-1018.19"
          },
          {
            "binary_name": "linux-modules-extra-6.8.1-1018-realtime",
            "binary_version": "6.8.1-1018.19"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.8.1-1018-realtime",
            "binary_version": "6.8.1-1018.19"
          },
          {
            "binary_name": "linux-realtime-cloud-tools-6.8.1-1018",
            "binary_version": "6.8.1-1018.19"
          },
          {
            "binary_name": "linux-realtime-headers-6.8.1-1018",
            "binary_version": "6.8.1-1018.19"
          },
          {
            "binary_name": "linux-realtime-tools-6.8.1-1018",
            "binary_version": "6.8.1-1018.19"
          },
          {
            "binary_name": "linux-tools-6.8.1-1018-realtime",
            "binary_version": "6.8.1-1018.19"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:Realtime:24.04:LTS",
        "name": "linux-realtime",
        "purl": "pkg:deb/ubuntu/linux-realtime@6.8.1-1018.19?arch=source\u0026distro=realtime/noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.8.1-1018.19"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.8.0-1008.19",
        "6.8.1-1001.1",
        "6.8.1-1002.2",
        "6.8.1-1003.3",
        "6.8.1-1004.4",
        "6.8.1-1005.5",
        "6.8.1-1006.6",
        "6.8.1-1007.7",
        "6.8.1-1008.8",
        "6.8.1-1009.9",
        "6.8.1-1010.10",
        "6.8.1-1011.11",
        "6.8.1-1012.12",
        "6.8.1-1013.14",
        "6.8.1-1014.15",
        "6.8.1-1015.16",
        "6.8.1-1016.17",
        "6.8.1-1017.18"
      ]
    }
  ],
  "aliases": [],
  "details": "In the Linux kernel, the following vulnerability has been resolved: ext4: don\u0027t set SB_RDONLY after filesystem errors When the filesystem is mounted with errors=remount-ro, we were setting SB_RDONLY flag to stop all filesystem modifications. We knew this misses proper locking (sb-\u003es_umount) and does not go through proper filesystem remount procedure but it has been the way this worked since early ext2 days and it was good enough for catastrophic situation damage mitigation. Recently, syzbot has found a way (see link) to trigger warnings in filesystem freezing because the code got confused by SB_RDONLY changing under its hands. Since these days we set EXT4_FLAGS_SHUTDOWN on the superblock which is enough to stop all filesystem modifications, modifying SB_RDONLY shouldn\u0027t be needed. So stop doing that.",
  "id": "UBUNTU-CVE-2024-50191",
  "modified": "2026-09-17T16:26:08Z",
  "published": "2024-11-08T06:15:00Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2024-50191"
    },
    {
      "type": "REPORT",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-50191"
    },
    {
      "type": "REPORT",
      "url": "https://git.kernel.org/linus/d3476f3dad4ad68ae5f6b008ea6591d1520da5d8"
    },
    {
      "type": "REPORT",
      "url": "https://git.kernel.org/stable/c/fbb177bc1d6487cd3e9b50ae0be2781b7297980d"
    },
    {
      "type": "REPORT",
      "url": "https://git.kernel.org/stable/c/4061e07f040a091f694f461b86a26cf95ae66439"
    },
    {
      "type": "REPORT",
      "url": "https://git.kernel.org/stable/c/58c0648e4c773f5b54f0cb63bc8c7c6bf52719a9"
    },
    {
      "type": "REPORT",
      "url": "https://git.kernel.org/stable/c/ee77c388469116565e009eaa704a60bc78489e09"
    },
    {
      "type": "REPORT",
      "url": "https://git.kernel.org/stable/c/d3476f3dad4ad68ae5f6b008ea6591d1520da5d8"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7166-1"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7166-2"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7166-3"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7186-1"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7186-2"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7194-1"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7166-4"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7276-1"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7277-1"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7310-1"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7383-1"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7384-1"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7385-1"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7386-1"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7383-2"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7384-2"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7403-1"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7451-1"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7468-1"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7523-1"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-7524-1"
    }
  ],
  "related": [
    "USN-7166-1",
    "USN-7166-2",
    "USN-7166-3",
    "USN-7186-1",
    "USN-7186-2",
    "USN-7194-1",
    "USN-7166-4",
    "USN-7276-1",
    "USN-7277-1",
    "USN-7310-1",
    "USN-7383-1",
    "USN-7384-1",
    "USN-7385-1",
    "USN-7386-1",
    "USN-7383-2",
    "USN-7384-2",
    "USN-7403-1",
    "USN-7451-1",
    "USN-7468-1",
    "USN-7523-1",
    "USN-7524-1"
  ],
  "schema_version": "1.7.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    },
    {
      "score": "medium",
      "type": "Ubuntu"
    }
  ],
  "upstream": [
    "CVE-2024-50191"
  ]
}

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.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

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.

Action not permitted

CVE-2024-50191 (GCVE-0-2024-50191)

CERTFR-2025-AVI-0349

Solutions

CERTFR-2025-AVI-0366

Solutions

FKIE_CVE-2024-50191

GHSA-639P-PGPG-5QR5

OESA-2024-2492 (CVE-2023-52920)

OESA-2025-1079 (CVE-2024-50191)

One crash stack for demonstration:

OPENSUSE-SU-2024:14500-1

OPENSUSE-SU-2025:14705-1

RHSA-2025:6966

UBUNTU-CVE-2024-50191 (CVE-2024-50191)

Tags

Sightings

Nomenclature

Related by attack behaviour