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

GCVE-1988-2026-0353

Vulnerability from gna-1988 – Published: 2026-09-11 07:55 – Updated: 2026-09-11 11:36
VLAI
Title
ASUS bsitf.sys (CVE-2026-13585): Arbitrary Physical Memory Mapping in ASUS Business/Software Manager kernel driver
Summary
Hi all, I'm disclosing a vulnerability (CVE-2026-13585) in the ASUS bsitf.sys / AsusBSItf.sys kernel driver, shipped with ASUS Business Manager and Software Manager. ASUS has assigned the CVE and published a vendor advisory with countermeasures. Summary: The driver exposes a device (\\.\bsitf, admin-required to open) with an IOCTL that allocates a caller-specified amount of physically contiguous kernel memory, maps it into the calling process, and returns both the user-space pointer and the physical address, with no validation on the requested size, no cap on allocation count, and no input checking. Observed impact: - Pool-exhaustion denial of service: uncapped allocations in a loop exhaust NonPagedPool and BSOD the machine, reachable from any admin process. - Physical address disclosure on every allocation, useful as an info-leak primitive or for DMA-oriented attacks. - On version 3.0.10.0 the pool type is executable (NonPagedPool), enabling shellcode staging at a known kernel address (still requires a separate control-flow bug). Later 3.1.x versions use NonPagedPoolNx, so this does not apply there. Affected versions tested: 3.0.10.0 (bsitf.sys), 3.1.10.0 and 3.1.25.0 (AsusBSItf.sys). All exhibit the same flaw. Timeline: - 2026-04-06: Discovered, PoC confirmed on Windows 11 24H2, reported to ASUS PSIRT - 2026-07-14: CVE assigned and case closed (CVE-2026-13585) - 2026-07-15: Vendor advisory and countermeasures released Full technical writeup and PoC: https://blog.ahmadz.ai/asus_bsitf_0_day_poc/ Regards, Rehman Ahmadzai _______________________________________________ Sent through the Full Disclosure mailing list https://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Impacted products
Vendor Product Version CPE status
Asus bsitf.sys CVE-2026-13585 Affected: unknown
guessed Create a notification for this product.
Relationships
analysis GCVE-1988-2026-0353 (this record)

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "bsitf.sys CVE-2026-13585",
          "vendor": "Asus",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Hayaturehman Ahmadzai"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Hi all,\n\nI\u0027m disclosing a vulnerability (CVE-2026-13585) in the ASUS bsitf.sys /\nAsusBSItf.sys kernel driver, shipped with ASUS Business Manager and\nSoftware Manager. ASUS has assigned the CVE and published a vendor advisory\nwith countermeasures.\n\nSummary: The driver exposes a device (\\\\.\\bsitf, admin-required to open)\nwith an IOCTL that allocates a caller-specified amount of physically\ncontiguous kernel memory, maps it into the calling process, and returns\nboth the user-space pointer and the physical address, with no validation on\nthe requested size, no cap on allocation count, and no input checking.\n\nObserved impact:\n\n- Pool-exhaustion denial of service: uncapped allocations in a loop exhaust\nNonPagedPool and BSOD the machine, reachable from any admin process.\n- Physical address disclosure on every allocation, useful as an info-leak\nprimitive or for DMA-oriented attacks.\n- On version 3.0.10.0 the pool type is executable (NonPagedPool), enabling\nshellcode staging at a known kernel address (still requires a separate\ncontrol-flow bug). Later 3.1.x versions use NonPagedPoolNx, so this does\nnot apply there.\n\nAffected versions tested: 3.0.10.0 (bsitf.sys), 3.1.10.0 and 3.1.25.0\n(AsusBSItf.sys). All exhibit the same flaw.\n\nTimeline:\n- 2026-04-06: Discovered, PoC confirmed on Windows 11 24H2, reported to\nASUS PSIRT\n- 2026-07-14: CVE assigned and case closed (CVE-2026-13585)\n- 2026-07-15: Vendor advisory and countermeasures released\n\nFull technical writeup and PoC: https://blog.ahmadz.ai/asus_bsitf_0_day_poc/\n\nRegards,\n\nRehman Ahmadzai\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-11T11:36:22Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description",
            "exploit"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jul/26"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Jul/26"
        },
        {
          "url": "https://blog.ahmadz.ai/asus_bsitf_0_day_poc/"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Jul/26"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "ASUS bsitf.sys (CVE-2026-13585): Arbitrary Physical Memory Mapping in ASUS Business/Software Manager kernel driver",
      "x_gcve": [
        {
          "recordType": "analysis",
          "relationships": [
            {
              "destId": "CVE-2026-13585",
              "type": "related"
            }
          ],
          "vulnId": "GCVE-1988-2026-0353",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jul/26",
            "automated": true,
            "contentSha256": "b4c5a9fd17e80b57571c3b7453eaf270fb7083679b5e452617a5ee20cce5c181",
            "evidenceScore": 9,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Jul/26",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-07-16T06:51:53Z"
          }
        },
        {
          "recordType": "advisory",
          "vulnId": "gcve-1988-2026-0353"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-09-11T07:55:57Z",
    "dateUpdated": "2026-09-11T11:36:22Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0353"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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

Sightings

Author Source Type Date Other

Nomenclature

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

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Related by attack behaviour

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


Loading…