• M
    Bluetooth: Verify that l2cap_get_conf_opt provides large enough buffer · a3dbdb59
    Marcel Holtmann 提交于
    mainline inclusion
    from mainline-5.0
    commit 7c9cbd0b5e38a1672fcd137894ace3b042dfbf69
    category: bugfix
    bugzilla: NA
    CVE: CVE-2019-3459
    
    -------------------------------------------------
    
    The function l2cap_get_conf_opt will return L2CAP_CONF_OPT_SIZE + opt->len
    as length value. The opt->len however is in control over the remote user
    and can be used by an attacker to gain access beyond the bounds of the
    actual packet.
    
    To prevent any potential leak of heap memory, it is enough to check that
    the resulting len calculation after calling l2cap_get_conf_opt is not
    below zero. A well formed packet will always return >= 0 here and will
    end with the length value being zero after the last option has been
    parsed. In case of malformed packets messing with the opt->len field the
    length value will become negative. If that is the case, then just abort
    and ignore the option.
    
    In case an attacker uses a too short opt->len value, then garbage will
    be parsed, but that is protected by the unknown option handling and also
    the option parameter size checks.
    Signed-off-by: NMarcel Holtmann <marcel@holtmann.org>
    Reviewed-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: NJohan Hedberg <johan.hedberg@intel.com>
    Signed-off-by: NYang Yingliang <yangyingliang@huawei.com>
    a3dbdb59
l2cap_core.c 179.1 KB